CTFL-Foundation ISTQB Certified Tester Foundation Level Questions and Answers

5 maturity levels

Focussed on higher level testing

20 key areas

Highly related to CMMI

Continuous model

Staged model

Focussed on component and integration testing

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

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.

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

High level of documentation

Failure Mode and Effect Analysis (FMEA) sessions

Traceability to requirements

Non-functional testing

Master test planning

Test design techniques

Reviews

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

(iii) and (ii)

(i) and (iv)

(ii) and (i)

(i) and (iii)

This question is impossible to answer

This question is easy to answer

The answer depends on the risk for your industry, contract and special requirements

This answer depends on the maturity of your developers

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

Quality of the specification

Availability of end-users

The costs of hardware and tools

Unknown input quality due to third party development

700

720

784

570

Test planning

Test execution

Test management

Test design

The quality of the development estimate may be poor.

In general bottom-up estimation is always better than top-down estimation.

The percentage based technique only applies to the V life cycle model.

Using the same percentage every time does not address the level of risk of the application to be tested.

The maturity of the organization, e.g. the quality of the test basis, quality of development testing, configuration management, availability of test tools, also influence the effort needed for testing.

It builds on large set of historical data

The result is almost always a too low estimate for the required test effort

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.

Component testing verifies the functioning of software modules, program objects, and classes that are separately testable, whereas system testing verifies interfaces between components and interactions with different parts of the system.

Test cases for component testing are usually derived from component specifications, design specifications, or data models, whereas test cases for system testing are usually derived from requirement specifications, functional specifications or use cases.

Component testing focuses on functional characteristics, whereas system testing focuses on functional and non-functional characteristics.

Component testing is the responsibility of the technical testers, whereas system testing typically is the responsibility of the users of the system.

By providing training in the payroll domain

By providing a workshop on test design techniques

By providing specific training on the systems being tested

By providing training on reviewing requirements

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

Product risks which have been mitigated and those which are outstanding.

Recommendations for taking controlling actions

Status compared against the started exit criteria

Detailed overview of the risk-based test approach being used to ensure the exit criteria to be achieved

(i) and (ii)

(i) and (iv)

(ii) and (iii)

(ii) and (iv)

16

2

1

63

All supported credit cards

Language localization

Valid and invalid advances

Usability

Response time

Brainstorming

Inspections

Expert interviews

Independent assessments

Planning and control, analysis, design, implementation, execution, evaluation of exit criteria and reporting, test closure.

Executing tests, identifying and recording defects and preparing recommendation and closure reports.

Controls, preparation of test cases, execution of test cases, execution of regression packs, communicating with developers, writing recommendations for release.

Static testing, dynamic testing, defect reporting, reporting and closure.

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.

Introduce mandatory evening and weekend working to retrieve the 3 week slippage.

Reconsider the exit criteria and review the test plan in the context of the current situation.

Advise the user community regarding the reduced scope of requirements and the additional incremental delivery.

Arrange a meeting with the user community representatives to discuss the user interface.

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

Identify test staff members that will be involved in the system test

Define test career paths

Understand the software development life cycle used by the software house

Assess the testing that needs to be done to minimize the risks

Issue the test strategy document for review

Define a master test plan template

Perform a project risk analysis

Integration with other tools

Learning time required to use the new tool

Tool portability

Evaluation of suitable tools

Suggested solution, priority and number of defects assigned to this developer.

Status of the incident, degree of impact, Test Case Number.

History, related defects and expected fix time.

Line of code, number of defects found, time of day.

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.

Percentage of business requirements exercised

Percentage of planned hours worked this week

Percentage of countries that have test scenarios

Percentage of test iterations completed

Test environment more complex

Define expectation for tasks and deliverables

Clear channels of communications

Possibly different cultures

Testing of non-functional requirements

Audit trail from requirements to test cases

Applying test automation

ISO 9126-1 ‘Software engineering- Product quality Part 1:

Quality model’ is an international standard, that provides a basis on which to define quality assurance solutions.

ISA 4126-1 ‘Software engineering- Product quality Part 1:

Quality model’ is an international standard, that provides a basis on which to define quality assurance solutions.

BS-7925-2 ‘Software testing. Software component testing is a national standard used internationally. It covers a number of testing techniques that may be useful both on component testing level and on system testing level.

SY-395-01 ‘Standard for East Coast Hospital software’ is a regional standard adapted from a national one. Besides hospital software, this standard ought to be used also by other types of software system in the region.

IEEE 829 ‘standard for software test documentation’ is an international standard to be following mandatory by all testing origination regardless of lifecycle models.

Test planning and control

Test implementation & execution

Evaluating exit criteria and reporting

Test project closure

Frequency 1, 5; Duration 1, 60

Frequency 0, 1, 5, 6; Duration 59 seconds, 1 minute, 60 minutes, 60 minutes 1 second

Frequency 0, 1, 5, 6; Duration 0, 1, 30, 60, 61

Frequency 0, 1, 2, 5, 6; Duration 0, 1, 30, 60, 61

The bidder’s test policy should enforce that incident management fully conforms to IEEE 1044.

The bidder’s project strategy shows that the data content of all the test environments conforms to EU standards.

The bidder’s test plan shows that the application will be delivered for acceptance in six months time.

The bidder’s project test plan depicts a phased implementation with later delivery dates to be confirmed and states that test deliverables will be developed using IEEE 829 as a guide.

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.

Title. End of Day failure.. Reproducible. Yes. Description. Script eod 1.4 fails when the first transaction of the day is a future dated transaction. Screen shot of the failure attached.

Title. Transaction input screen validation..Reproducible. Yes. Description. Script eod 1..4 fails . Screen shot of the failure attached. Validation of transaction entryon screen TRN-003B should not allow future dated transactions – see PID ver 1.3 para 10b iv.

Title. Screen TRN-003B validation of transaction date.. Reproducible. No. Description. When a future dated transaction is processed by the end of day process, a failure can occur. This does not always happen. Screen shot of the failure attached.

Title. Screen TRN-003B validation of transaction date. Reproducible. Yes. Description. Script eod 1.4 fails when the first transaction of the day is a future dated transaction. Screen shot of the failure attached. Validation of transaction entry on screen TRN-003B should not allow future dated transactions – see PID ver 1.3 para 10b iv.

Analysis and design of tests begins as soon as development is completed.

Some, but not all, development activities have corresponding test activities.

Each test level has test objectives specific to that level.

All document reviews involve the development team.

The percentage of decision coverage achieved during unit testing.

The availability of the latest version of the capture-replay tool (for testing the interface with the newly developed test management tool).

The sign-off of a performance test software release note (test item transmittal report) by both development and testing showing that system performance meets the specified acceptance criteria.

The percentage of acceptance test procedures scheduled for execution.

The percentage of requirements coverage achieved during system integration test.