Free ISQI-CTFL Exam Dumps Preview

Brainstorming

Expert interviews

Independent assessments

To know when a specific test has finished its execution

To ensure that the test case specification is complete

To set the criteria used in generating test inputs

To know when test planning is complete

Prepare and acquire the test data

Set up and check the test environment

Write test summary reports

No, the problem is not with testers

Both a & b

None of the above

Integration with other tools

Learning time required to use the new tool

Evaluation of suitable tools

(i), (ii), (vi).

(ii), (iii), (v).

(i), (iv), (v).

Structure based testing

Specification based testing

Use Case testing

Outsourcing test design and execution to a different company

Having the company's independent test team design and execute the tests

Minimizing contact between testers and developers during test design to avoid bias

Give product risk status

Show trend analysis

State recommendations for release

f, g, a, c, b, d, e, i, j, h

e, i, a, c, b, d, f, g, h, j

e, i, f, g, a, c, b, d, h, j

(i) and (ii)

(i) and (iv)

(iii) and (iv)

Decision Coverage

Error Guessing

Statement Coverage

System retirement

System modification

Introduction of a test management tool

Decision Table Testing

Boundary Value Analysis

Error Guessing

i, ii & iv are true, iii & v are false.

iv & v are true, i, ii & iii are false.

i, ii & iii are true iv & v are false.

Test training needs for the project resources

Test performance indicators

The test schedule

700

784

570

State transition testing.

Decision table testing.

Statement testing.

Use case testing

Boundary value testing

Statement testing and coverage

All the planned tests have been run

Time has run out

All faults have been fixed correctly

Both A and C

iii is true, i, ii, iv & v are false

iii & iv are true. i, ii & v are false

i, iii, iv & v are true, ii us false

i & iii are true, ii, iv & v are false

Preventing defects from being introduced into the code

Investigating and fixing defects in the software under test

Gaining confidence that the system is fit-for-purpose

The expectation is that development testing is not adequate.

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

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

level.

Underestimating the demand for a tool.

The purchase price of the tool.

The cost of resources to implement and maintain the tool.

Top down

Bottom up

Functional incrementation.

Use a tool in order to help define a good test process because the tool will force process repeatability

and therefore enforce good test process.

Always start by bringing in automated test execution tools as these tools have the greatest return on

investment and therefore should be introduced first.

Allow the developers to select the testing tools because tools are technical and developers have the

appropriate skills to advise on test tool selection and configuration.

This question is impossible to answer

This question is easy to answer

This answer depends on the maturity of your developers

Acceptance criteria, completion criteria, pass/fail criteria.

The last executable statement within a component.

Cost overruns.

Developer and independent testing will overlap and waste resources.

Independent testers need extra education and always cost more.

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

Test design specification

Test condition

Test case specification

Detection of failures not easily found by other types of testing

Detection of suspicious operations caused by deviations from regulations

Detect deviations in standards by executing the source code

A statement of test objectives and test ideas on how to test.

The process of identifying differences between the actual results and the expected results for a test.

All documents from which the requirements of a component or system can be inferred.

Statement testing and exploratory testing

Decision testing and equivalence partitioning

Decision testing and decision table testing

Component testing

System testing

User acceptance testing

Regression testing is checking that the reported defect has been fixed; retesting is testing that there

are no additional problems in previously tested software.

Regression testing is checking there are no additional problems in previously tested software; retesting

enables developers to isolate the problem.

Regression testing involves running all tests that have been run before; retesting runs new tests.

The system will fail, causing a defect

Loss of money, time, or business reputation

Contractual requirements have not been met by testing

Inspection

Walkthrough

Informal review

Test procedure

Test execution schedule

Test condition

Outsourcing of test automation based on an offer from an Asian company, AsiaAutoTest, which has

people who are specialists in system level capture-replay automation tools. They also offer training and besides they offer to run and maintain the regression tests in the future.

Internal offer from the development department of XYZ to create the regression package using CppUnit

as test automation tool. One of the development groups have very good experiences in automating unit tests, and they are willing to do training as well.

Solution from a tool vendor offering to educate two test team members in the use of their easy-to-use

test automation capture replay tool over the first 3 month and based on that build the regression test suite. In addition to Vicki, Steve is the only one that has time available to be educated.

Automated tests are better than manual tests for avoiding the Exhaustive Testing.

Exhaustive testing is, with sufficient effort and tool support, feasible for all software.

The purpose of testing is to demonstrate the absence of defects. The purpose of testing is to

demonstrate the absence of defects.

To immediately save cost for current projects in your organization

To show competitors that your organization is improving its test process

To motivate the test team and make testers feel valued

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

Define test career paths

Define a master test plan template

Perform a project risk analysis

We can never be certain that the program is bug free

We have no definite stopping point for testing, which makes it easier for some managers to argue for

very little testing

We have no easy answer for what testing tasks should always be required, because every task takes

time that could be spent on other high importance tasks

At the beginning of the project

As soon as requirements have been approved

At any time before UAT begins

Testing can demonstrate that there are no defects

Testing can demonstrate that the software is correct

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

Frequency 1, 5; Duration 1, 60

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

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

Increase software quality;

Enable those responsible for software failures to be identified;

Show there are no problems remaining?

Defining the amount, level of detail structure, and templates for the test documentation.

Adequacy of the test approaches taken.

Discussions on disaster recovery.

Applying to time-related data classes only.

A form of white-box testing.

A method to reduce test coverage.

We can never be certain that the program is bug free.

We have no definite stopping point for testing, which makes it easier for some managers to argue for

very little testing.

We have no easy answer for what testing tasks should always be required, because every task takes

time that could be spent on other high importance tasks.

They should start test analysis when the corresponding development level is complete

They should be involved in reviewing requirements or user stories as soon as drafts are available

They should ensure the same test objectives apply to each test level