CTFL_001 ISTQB Certified Tester Foundation Level Exam

 

Audience
The Foundation Level syllabus forms the basis of the International Software Testing Qualifications Board (ISTQB®) Certified Tester Scheme.

ISTQB® Foundation Level is relevant across software delivery practices including Waterfall, Agile, DevOps and Continuous Delivery.

The 2018 Foundation Level qualification is suitable for anyone who needs to demonstrate practical knowledge of the fundamental concepts of software testing including people in roles such as testers, test analysts, test engineers, test consultants, test managers, user acceptance testers and software developers.

It is also appropriate for individuals who need a basic understanding of software testing including project managers, quality managers, software development managers, business analysts, IT directors and management consultants.

The new 2018 syllabus is recognised as a pre-requisite to other ISTQB® certifications where Foundation Level is required (note: all previous releases of Foundation Level, including the 2011 syllabus and “grandfathered” Foundation Level certifications, will remain valid).

Training for 2018 Certified Tester Foundation Level is available from Accredited Training Providers (classroom, virtual and e-learning). We highly recommend attending accredited training as an ISTQB® Member Board will have assessed the materials for relevance and consistency against the syllabus. Information about Accredited Training Providers can be found here or contact your local ISTQB® Member Board or Exam Provider

Self-study, using the syllabus and recommended reading material, is also an option when preparing for the Foundation Level exam. Your local ISTQB® Member Board or Exam Provider will be able to provide information on exams e.g. languages available, where to find an exam centre etc.

Have a look at the Foundation Level introduction video.

Business Outcomes
The Business Outcomes expected of a candidate who has achieved the 2018 Foundation Level certification are as follows:

Promote efficient and effective communication by using a common vocabulary for software testing.
Understand fundamental concepts of software testing.
Demonstrate understanding of how different development and testing practices, and different constraints on testing, may apply in optimizing testing to different contexts.
Contribute effectively in reviews.
Use established techniques for designing tests at all test levels.
Interpret and execute tests from given test specifications. Report on test results.
Understand test management principles for resources, strategies, planning, project control and risk management
Write and communicate clear and understandable defect reports
Understand the project factors that drive the test priorities and test approach
Understand the value that software testing brings to stakeholders
Appreciate how testing activities and work products align with project objectives, measures and targets
Assist in the selection and implementation process of testing tool

Learning Objectives
Learning objectives are indicated for each section in the syllabus and classified as follows:

K1: remember, recognize, recall
K2: understand, explain, give reasons, compare, classify, categorize, give examples, summarize
K3: apply, use
K4: analyze

There are 62 Learning objectives in the 2018 Foundation syllabus:

15 K1
40 K2
7 K3

The 2018 Foundation Level Learning objectives are as follows:
Chapter 1 Fundamentals of Testing

1.1 What is Testing?
LO-1.1.1 Identify typical objectives of testing (K1)
LO-1.1.2 Differentiate testing from debugging (K2)

1.2 Why is Testing Necessary?
LO-1.2.1 Give examples of why testing is necessary (K2)
LO-1.2.2 Describe the relationship between testing and quality assurance and give examples of how testing contributes to higher quality (K2)
LO-1.2.3 Distinguish between error, defect, and failure (K2)
LO-1.2.4 Distinguish between the root cause of a defect and its effects (K2)

1.3 Seven Testing Principles (K2)
LO-1.3.1 Explain the seven principles of testing (K2)

1.4 Test Process
LO-1.4.1 Explain the impact of context on the test process (K2)
LO-1.4.2 Describe the test activities and respective tasks within the test process (K2)
LO-1.4.3 Differentiate the work products that support the test process (K2)
LO-1.4.4 Explain the value of maintaining traceability between the test basis and the test work products (K2)

1.5 The Psychology of Testing (K2)
LO-1.5.1 Identify the psychological factors that influence the success of testing (K1)
LO-1.5.2 Explain the difference between the mindset required for test activities and the mindset required for development activities (K2)
Chapter 2 Testing Throughout the Software Development Lifecycle

2.1. Software Development Lifecycle Models
LO-2.1.1 Explain the relationships between software development activities and test activities in the software development lifecycle (K2)
LO-2.1.2 Identify reasons why software development lifecycle models must be adapted to the context of project and product characteristics (K1)
LO-2.1.3 Recall characteristics of good testing that are applicable to any life cycle model (K1)

2.2 Test Levels (K2)
LO-2.2.1 Compare the different test levels from the perspective of objectives, test basis, test objects, typical defects and failures, and approaches and responsibilities (K2)

2.3 Test Types (K2)
LO-2.3.1 Compare functional, non-functional and white-box testing (K2)
LO-2.3.2 Recognize that functional and structural tests occur at any test level (K1)
LO-2.3.3 Recognize that functional, non-functional and white-box tests occur at any test level (K1)
LO-2.3.4 Compare the purposes of confirmation testing and regression testing (K2)

2.4 Maintenance Testing (K2)
LO-2.4.1 Summarize triggers for maintenance testing (K2)
LO-2.4.2 Describe the role of impact analysis in maintenance testing (K2)
LO-2.4.3 Describe the role of impact analysis in maintenance testing (K2)
Chapter 3 Static Testing

3.1 Static Testing Basics
LO-3.1.1 Recognize types of software work product that can be examined by the different static testing techniques (K1)
LO-3.1.2 Use examples to describe the value of static testing (K2)
LO-3.1.3 Explain the difference between static and dynamic techniques, considering objectives, types of defects to be identified, and the role of these techniques within the software lifecycle (K2)

3.2 Review Process
LO-3.2.1 Summarize the activities of the work product review process (K2)
LO-3.2.2 Recognize the different roles and responsibilities in a formal review (K1)
LO-3.2.3 Explain the differences between different review types: informal review, walkthrough, technical review and inspection (K2)
LO-3.2.4 Apply a review technique to a work product to find defects (K3)
LO-3.2.5 Explain the factors that contribute to a successful review (K2)

Chapter 4 Test Techniques

4.1 Categories of Test Techniques
LO-4.1.1 Explain the characteristics, commonalities, and differences between black-box test techniques, white-box test techniques and experience-based test techniques (K2)

4.2 Black-box Test Techniques
LO-4.2.1 Apply equivalence partitioning to derive test cases from given requirements (K3)
LO-4.2.2 Apply boundary value analysis to derive test cases from given requirements (K3)
LO-4.2.3 Apply decision table testing to derive test cases from given requirements (K3)
LO-4.2.4 Apply state transition testing to derive test cases from given requirements (K3)
LO-4.2.5 Explain how to derive test cases from a use case (K2)

4.3 White-box Test Techniques
LO-4.3.1 Explain statement coverage (K2)
LO-4.3.2 Explain decision coverage (K2)
LO-4.3.3 Explain the value of statement and decision coverage (K2)

4.4 Experience-based Test Techniques
LO-4.4.1 Explain error guessing (K2)
LO-4.4.2 Explain exploratory testing (K2)
LO-4.4.3 Explain checklist-based testing (K2)

Chapter 5 Test Management

5.1 Test Organization
LO-5.1.1 Explain the benefits and drawbacks of independent testing (K2)
LO-5.1.2 Identify the tasks of a test manager and tester (K1)

5.2 Test Planning and Estimation
LO-5.2.1 Summarize the purpose and content of a test plan (K2)
LO-5.2.2 Differentiate between various test approaches (K2)
LO-5.2.3 Give examples of potential entry and exit criteria (K2)
LO-5.2.4 Apply knowledge of prioritization, and technical and logical dependencies, to schedule test execution for a given set of test cases (K3)
LO-5.2.5 Identify factors that influence the effort related to testing (K1)
LO-5.2.6 Explain the difference between two estimation techniques: the metrics-based technique and the expert-based technique (K2)

5.3 Test Monitoring and Control
LO-5.3.1 Recall metrics used for testing (K1)
LO-5.3.2 Summarize the purposes, contents, and audiences for test reports (K2)

5.4 Configuration Management
LO-5.4.1 Summarize how configuration management supports testing (K2)

5.5 Risks and Testing
LO-5.5.1 Define risk level by using likelihood and impact (K1)
LO-5.5.2 Distinguish between project and product risks (K2)
LO-5.5.3 Describe, by using examples, how product risk analysis may influence thoroughness and scope of testing (K2)

5.6 Defect Management
LO-5.6.1 Write a defect report, covering defects found during testing (K3)

Chapter 6. Tool Support for Testing

6.1 Test tool considerations
LO-6.1.1 Classify test tools according to their purpose and the test activities they support (K2)
LO-6.1.2 Identify benefits and risks of test automation (K1)
LO-6.1.3 Remember special considerations for test execution and test management tools (K1)

6.2 Test Planning and Estimation (K3)
LO-6.2.1 Identify the main principles for selecting a tool (K1)
LO-6.2.2 Recall the objectives for using pilot projects to introduce tools (K1)
LO-6.2.3 Identify the success factors for evaluation, implementation, deployment and on-going support of test tools in an organization (K1)

Syllabus
The Foundation Level Syllabus forms the basis for the International Software Testing Qualification at the Foundation Level.

The International Software Testing Qualifications Board® (ISTQB®) provides it to the national examination bodies for them to accredit the training providers and to derive examination questions in their local language.

Training providers will produce courseware and determine appropriate teaching methods for accreditation, and the syllabus will help candidates in their preparation for the examination.
The Certified Tester Foundation Level in Software Testing

The Foundation Level qualification is aimed at anyone involved in software testing. This includes people in roles such as testers, test analysts, test engineers, test consultants, test managers, user acceptance testers and software developers.

This Foundation Level qualification is also appropriate for anyone who wants a basic understanding of software testing, such as project managers, quality managers, software development managers, business analysts, IT directors and management consultants. Holders of the Foundation Certificate will be able to go on to a higher level software testing qualification.

The Foundation Level Syllabus 2018 is available in Materials for download section.

QUESTION 1
You are about to release a test progress report to a senior manager, who is not a test specialist. Which of the following topics should NOT be included in the test progress report?

A. Product risks which have been mitigated and those which are outstanding.
B. Recommendations for taking controlling actions
C. Status compared against the started exit criteria
D. Detailed overview of the risk-based test approach being used to ensure the exit criteria to be achieved

Correct Answer: D

QUESTION 2
Explain how the above mentioned report may differ from a report that you produce for the project manager, who is a test specialist Select TWO items from the following options that can be used to report to the project
manager and would not be included in a report to senior management.

A. Show details on effort spent
B. List of all outstanding defects with their priority and severity
C. Give product risk status
D. Show trend analysis
E. State recommendations for release

Correct Answer: AB

QUESTION 3
Consider the typical objectives of testing. Which of the following metrics can be used to measure the effectiveness of the testing process in achieving one of those objectives?

A. Average number of days between defect discovery and resolution
B. Percentage of requirements covered
C. Lines of code written per developer per day
D. Percentage of test effort spent on regression testing

Correct Answer: B

QUESTION 4
You have been given responsibility for the non-functional testing of a safety-critical monitoring & diagnostics
package in the medical area. Which of the following would you least expect to see addressed in the test plan?

A. Availability
B. Safety
C. Portability
D. Reliability

Correct Answer: C

QUESTION 5
Since the system is in the medical domain and therefore in the safety critical area, testing needs to be rigorous
and evidence is required that the system has been adequately tested. Identify THREE measures that would
typically be part of the test approach in this domain and which are not always applicable in other domains!

A. High level of documentation
B. Failure Mode and Effect Analysis (FMEA) sessions
C. Traceability to requirements
D. Non-functional testing
E. Master test planning
F. Test design techniques
G. Reviews

Correct Answer: ABC

Actualkey ISTQB CTFL_001 Exam pdf, Certkingdom ISTQB CTFL_001 PDF

Best ISTQB CTFL_001 Certification, ISTQB CTFL_001 Training at certkingdom.com