CTFL-Foundation ISTQB Certified Tester Foundation Level Question and Answers

Test planning and control

Test implementation & execution

Evaluating exit criteria and reporting

Test project closure

Percentage of business requirements exercised

Percentage of planned hours worked this week

Percentage of countries that have test scenarios

Percentage of test iterations completed

Developer and independent testing will overlap and waste resources.

Developers loose the sense of responsibility and independent testers may become a bottleneck.

Independent testers need extra education and always cost more.

Independent testers will become a bottleneck and introduce problems in incident management.

i, ii, iv, vi

ii, i, v, vi

ii, v, i, iii

i, iv, v, vi

Code cannot be released into production until independent testing is complete.

Testing is isolated from development.

Independent testers find different defects and are unbiased.

Developers do not have to take as much responsibility for quality.

It’s a testing design technique based in the internal software structure.

It’s a static test design technique.

It’s a testing design technique to verify decisions.

It’s a testing design technique based in the system requirements.

a, f and g.

b, c and f.

a, c and d.

d, e and g.

Statement coverage = 3, Decision coverage = 3

Statement coverage = 2, Decision coverage = 2

Statement coverage = 1, Decision coverage = 2

Statement coverage = 2, Decision coverage = 1

Integration with other tools

Learning time required to use the new tool

Tool portability

Evaluation of suitable tools

Has there been sufficient comparison of tools?

What are the problems we are trying to address?

Do we have a set of tool requirements to validate the tool against?

How will the implementation be organized?

Which project will be selected to perform the tool pilot?

Is customized training available?

How will the change process be managed?

Average number of days between defect discovery and resolution

Percentage of requirements covered

Lines of code written per developer per day

Percentage of test effort spent on regression testing

No priority or severity assigned

Incident numbering is manual rather than automated

No mentioning of reproduceability

No classification on type of incident

Acceptance testing to verify the business process

Acceptance testing to verify operational requirements

Requirements testing as part of testing regulatory compliance

Another system test cycle to verify defect resolution

All supported credit cards

Language localization

Valid and invalid advances

Usability

Response time

The system will fail, causing a defect

If the defect is executed, the system may fail

Loss of money, time, or business reputation

Contractual requirements have not been met by testing

System and Component test levels only

All 'Developement' test levels, i.e. those before Acceptance testing

Component and Component integration test levels only

All test levels

Stress testing

Maintenance testing

Load testing

Usability testing

Test planning

Test execution

Test management

Test design

Quality of the specification

Availability of end-users

The costs of hardware and tools

Unknown input quality due to third party development

Test planning, test case preparation and test execution for each of the four iterations

Work should be explicitly allocated to test completion, test management, installation and to training on using the system

Activities to deploy the system in the user environment

Regression testing in the second, third and fourth iterations

Development activities for unit and integration testing

Reviews on requirements documentation

Defining test environment requirements for system testing

The concerns over the user interface may lead to changes to the interface which cannot be implemented by development in time for the second test iteration.

The concerns over the user interface raises the likelihood of a risk in that area and increases the amount of test effort needed for the user interface, thereby limiting the test effort available for other parts of the test management tool.

The delivery of the application without the interface changes may upset the user community.

The method used for test estimation is not accurate enough and hence the money spent on testing exceeded its budget.

Criteria A = OK, criteria B = OK, criteria C = OK

Criteria A = NOT OK, criteria B = NOT OK, criteria C = OK

Criteria A = OK, criteria B = NOT OK, criteria C = NOT OK

Criteria A = NOT OK, criteria B = NOT OK, criteria C = NOT OK

(i) and (ii)

(i) and (iv)

(ii) and (iii)

(ii) and (iv)

The skills and experience of developers to correct the failures.

The standards used for the requirements specification.

The metrics recorded from testing the capture-replay tool.

The number of testers in the company and their grade.

16

2

1

63

Component testing: decision testing; System testing: exploratory testing

Component testing: decision testing; System testing: decision table testing

Component testing: statement testing; System testing: equivalence partitioning

Component testing: statement testing; System testing: decision table partitioning

In the delivered application, one of the countries, as specified in the requirements, has not been correctly implemented.

The application takes too long to process a request for additional cover.

The test cases do not cover the key requirements.

The successful bidder may not deliver all the required functionality on time.

a

b

c

d

e

f

The expectation is that development testing is not adequate.

Exit criteria are used to decide on when to stop testing.

Entry and exit criteria are a principal way for getting adequate resources.

Using entry and exit criteria will prevent software that is not or poorly tested from going to the next test level.

a

b

c

d

e

f

Create an estimate based on the function point analysis technique and test point analysis

Create an estimate based on the complexity of the code

Create an estimate based on the credentials of the successful bidder

Create an estimate based on a percentage of the development effort

Easier to quickly adapt testing to changing requirements compared to experienced-based testing

Targets certain types of faults

Will guide experienced testers to find defects

Provides a way to differentiate depth of testing based on product risks by using different techniques

More enhanced documentation and therefore higher repeatability and reproducibility

Will make non-systematic testing redundant

Will reduce the need for early reviews

A test strategy should address identified generic product risks and present a process for mitigating those risks in line with the testing policy.

A test strategy identifies the specific product for a project risk and defines the approach for the test project.

A test strategy is derived from the test policy and describes the way risk assessments are performed in projects.

A test strategy is the result of a project risk analysis and defines the approach and resources for testing.

Defects

Trends analysis

Test Effectiveness

Time Spent Testing

Status accounting of configuration items

Auditing conformance to ISO9001

Identification of test versions

Record of changes to documentation over time

Controlled library access

Planning and control

Test closure activities

Analysis and design

None

A person with the ability to complete tasks

A quality assurance officer

A person with in-depth technical skills

A person who brings new ideas to the team

Provide more time for testing in the schedule

Allow people to take some time off

Introduce entry criteria to the testing phase

Organize a meeting with senior management in which they address the importance of good testing for this project

They are a cheap resource

They have good testing skills

This can serve as a way to build their confidence in the system

They have the ability to also focus on invalid test cases

ISO 9126

IEEE 829

BS 7925/2

DO-178B

If the scope of test performance improvement covers all test levels, TMMi is preferred since TPI focusses mainly on black-box testing.

If the organization is already applying CMMI, TMMi may be preferred since it has the same structure and uses the same terminology. TMMi addresses management commitment very strongly and is therefore more suitable to support a top-down improvement process.

TPI is much more a bottom-up model that is suitable for addressing test topics for a specific (test) project.

TMMi can only be used with the traditional V model,whereas TPI can be used with all types of software life cycles.

Synchronized with the overall long-term organizational strategy

Defined according to the maturity model used

Most visible to stakeholders

Low costs actions first