iSQI CTFL_Syll2018 ISTQB Certified Tester Foundation Level (Syllabus 2018) Exam Practice Test

Memory is leaking

Features are only partially implemented

Data structures that are used before initialization

Division by zero

Defect debugging and resolution

The outcome of testing of previous test cycle

Characteristics of the development process

Characteristics of the product

The key to high quality test documentation regimes is strict adherence to this standard

Any deviation from this standard should be approved by management, marketing & development

This test plan outline is relevant for military projects For consumer market projects there is a different specification with fewer items

Most test documentation regimes follow this spec to some degree, with changes done to fit a specific situation or organization

Percentage of work done in test environment creation

Average number of expected defects per requirement

Number of test cases run

Deviation from test milestone dates

Finding defects

Providing information for decision-making

Analyzing and removing the cause of failures

Gaining confidence about the level of quality of the software

The evaluation of a risk-management tools to decide which tool to use for future projects

The focus of testing is shifted to an area in the system where tests find with more defects than expected

Brainstorming sessions are held with a wide variety of stakeholders to identify possible failures in the system

Tests are prioritized to ensure that those associated with critical parts of the system are executed earlier

Pair programming is done with developer and tester pairing together

Pair programming is an alternative term for code inspection.

Pair programming is used usually in waterfall model

Pair programming is, among other things, an informal review method.

Add an impact analysis

Add information about which developer should fix the bug

Add the time stamp when the incident happened

Add information about which web browser was used

By customers or potential customers at their own locations

By an independent test team at the developing organization's location

At the developing organization's site, but not by the developing team

By customers or potential customers at the developing organization's site

The phenomena where a piece of code that has a lot of bugs is likely to have more hidden, yet unfound

The decreasing efficiency of debugging when done in code that has many bugs

Reduced effectiveness of test cases that are repeated and focused on the same scenarios

The redundancy of testing the same objects in both black and white box techniques

Performing a review of the requirement specifications before implementing the system can enhance quality

The testing of software demonstrates the absence of defects

Properly designed tests that pass reduce the level of risk in a system

Software testing identifies defects, which can be used to improve development activities.

7 and 13 are boundary values for the equivalence partition including age 10.

Thursday is a valid input boundary value

A minimum of 6 valid test cases are derived from boundary value analysis based on input age

$3.01 is a valid output boundary value

Reliability Testing

Confirmation Testing

Maintainability Testing

Regression Testing

System integration testing is testing non-functional requirements Acceptance testing concentrates on the functionality of the system

System integration testing is executed by the developers. Acceptance testing is done by the customer

System integration testing verifies that a system interfaces correctly with other systems. Acceptance testing verifies compliance to requirements

System integration testing verifies compliance to requirements Acceptance testing verifies correct interaction with other systems existing in the user's environment

Regression tests

Non-functional tests

Structural tests

Unit tests

Intrusive test tools are tools that do not exhibit the probe-effect

Testing tools can be used by both developers and testers

Use of testing tools is effective only when done as part of a test automation system

Testing tools allow developers do testing Use of such tools changes the role of the test team

Component testing

Acceptance tests

Maintenance testing

System tests

A variable is defined but is then not used

A variable is used in a calculation before it is defined

A variable has the wrong numeric value passed into it

A variable is used but not declared

a & d

a & b

b & c

c & d

I, II

II, III

I.IV

III. IV

Structure-based testing

Experience-based testing

Decision coverage testing

Specification-based testing

The expected result for the list friends response time was less than 10 seconds, whereas the average response time obtained was 13 seconds.

The user interface was complicated and confusing and I found it quite difficult to follow the test script.

The updates made as part of the add new member' function did not reflect the expected change as the name was written into the address field.

SQL injection into the username entry field allowed a variety of SQL commands to be executed by the application without the appropriate authority

Statement testing and exploratory testing

Decision testing and equivalence partitioning

Decision testing and decision table testing

Boundary value analysis and decision table testing

One of the topics that needs to be covered in the final Test Report.

A general name for test data that is used by the test cases.

A detailed description of a test case to enable its execution by non-expert tester.

A test environment comprised of stubs and drivers needed to execute a test.

TC1 - £23 total charges including buggy hire; TC2 - £21 total charge including buggy hire

TC1 - £18 total charges including buggy hire; TC2 - £16 total charge but no buggy allowed

TC1 - £23 total charges including buggy hire; TC2 - £16 total charge but no buggy allowed

TC1 - £17 total charges but no buggy allowed; TC2 - £21 total charge including buggy hire

Functional testing.

Non-functional testing.

Performance testing.

Structural testing.

Provides developers with information to isolate the failure.

Does not belong to an incident report

Provides Project Managers with information on the project risks.

Provides test managers with information to report test progress.

The metrics-based technique finds the most similar former project and uses its original estimate for the current project.

The expert-based approach is based on the experience of the owners of the testing tasks or by subject matter experts.

The metrics-based technique uses metrics supplied by the current test team based on their subjective feel for effort required.

In an expert-based approach, the test lead with the most years in the role is chosen to produce the estimate.

8

4

16

12

Reduce the number of tests needed to test the system

Assess of the correctness of key statements in each module of the application

Increase the percentage of executable statements that are exercised by a test set

Assess the number of code statements needed to implement each feature

Less than 0. 1 to 79, 80 and more than 80

Less than 0. 1 to 80, more than 80

Less than 1. 1 to 80, more than 80

Less than 1. 1 to 79, more than 80

Boundary value analysis

Use case testing

Equivalence partitioning

Decision table testing

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.

The number of staff available to execute tests

The level of detail in the test plan

The requirements for reliability and security in the product

The test estimation method used

Exploratory testing

Decision table testing

State transition testing

Statement testing

Determine differences between files or databases.

Monitor and report on how a system behaves under a variety of conditions.

Find defects, such as memory leaks, while software is executing.

Measure the percentage of specific types of code structure that have been exercised.

Likelihood of failure = 1%, potential cost of impact = $1m.

Likelihood of failure = 10%, potential cost of impact = $500,000.

Likelihood of failure = 20%, potential cost of impact = $150,000.

Likelihood of failure = 5%, potential cost of impact = $500,000.

Data-driven testing cannot be used with test execution tools

Recorded manual tests may become unstable in use

Keyword-driven testing cannot be used with test execution tools

Expected results for tests are not required because the tool generates expected results

The decision between using white or black box test techniques.

Executing software to validate the most common path through the code.

A technique to find defects in software source code and software models, performed without executing code.

It is a testing technique used during system testing.

a and e

b and c

d and e

a and b

Spelling mistake on an error message

A potential infinite loop

Memory leakage

A variable set to the wrong value

Equivalence partitioning

State transition testing

Boundary value analysis

Statement coverage

Yes, it’s strongly recommended.

No, risk analysis and priorities should be used to focus testing efforts

Yes, and it’s also necessary to include all the exit combinations

Only the expert testers can make exhaustive tests.

Testing can demonstrate that there are no defects

Testing can demonstrate that there are defects

Testing can demonstrate that the software is correct

Testing can demonstrate that there are no hidden defects in the software

Independent testers within the development teams

Independent testers from the user community

Independent test specialists for specific test types, such as usability, performance or certification test specialists

Code tested by another developer from the development team

Correcting defects

Locating defects in the code

Preventing defects

Ensuring no defects are present

Technical Review

Inspection

Walkthrough

Informal review