CTFL-Foundation Questions and Answers

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

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.

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

An approach to regression testing

A list of boundary values for “advance amount”

A description of dependencies between test cases

A logical collection of test cases

Functional testing to test security at the system level, load testing at the system level to ensure the system availability is acceptable, regression testing at all levels, structure based testing at the component level only

Functional testing to test the use cases at component level, reliability testing to test availability at the integration level, regression testing at the system testing level only, structure based testing at all levels

Functional testing of the use cases at system level, load testing at component level to ensure availability is acceptable, regression testing at the system and acceptance levels only, and structure based testing at the integration level only

Functional testing to test security at the acceptance level, load testing at the acceptance test level to ensure availability is acceptable, regression testing at the acceptance level only to ensure late changes are made correctly, and structure based testing at the component level

Because independent testers make fewer assumptions than developers

Because independent testers are isolated from the development team

Because independent testers can verify assumptions made during specification and implementation of the system

Because independent testers have a greater sense of responsibility for quality than developers

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

Executing the software work product

Manually examining the code or project documentation

Automated analysis of the code or project documentation

Manual examination and automated analysis of code or project documentation

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

The entry and exit criteria for each test phase

Test training needs for the project resources

The test design techniques to be used

Test performance indicators

The test schedule

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.

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

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.

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

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

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

a

b

c

d

e

f

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

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

High level of documentation

Failure Mode and Effect Analysis (FMEA) sessions

Traceability to requirements

Non-functional testing

Master test planning

Test design techniques

Reviews

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

No priority or severity assigned

Incident numbering is manual rather than automated

No mentioning of reproduceability

No classification on type of incident

It will extend the development team’s abilities and enhance future delivery capabilities.

It will allow the marketing, clerical and testing staff to validate and verify the early screen prototypes.

Time-box constraints will guarantee code releases are delivered on schedule.

More time can be spent on test execution as less formal documentation is required.

Decision Table Testing

Boundary Value Analysis

Error Guessing

Exploratory Testing

Percentage of business requirements exercised

Percentage of planned hours worked this week

Percentage of countries that have test scenarios

Percentage of test iterations completed

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.

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.

A description of how the test cases are cross-referenced to requirements in the test management tool.

A detailed identification of the resources that will carry out structural testing in the first iteration.

The test approach that will be applied at system integration testing.

A list of the names of the testers who will carry out the performance testing for the final iteration.

The process of testing an integrated system to verify that it meets specified requirements.

The process of testing to determine the compliance of a system to coding standards.

Testing without reference to the internal structure of a system.

Testing system attributes, such as usability, reliability or maintainability.

Determine whether enough component testing was executed.

Cause as many failures as possible so that faults can be identified and corrected.

Prove that all faults are identified.

Prove that any remaining faults will not cause any failures.

Unit testing, system testing, acceptance testing, maintenance testing.

System testing, unit testing, acceptance testing, maintenance testing.

Acceptance testing, system testing, maintenance testing, unit testing.

Unit testing, maintenance testing, system testing, acceptance testing.

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

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?

a & d

a & b

b & c

c & d

The predicted number of defects and the amount of rework required

The ratio of developers to testers in the project team

The planned use of a project management tool to schedule tasks

The responsibilities for testers and developers being clearly defined

0600, 1000, 1200

1001, 1300, 2259

0100, 0800, 2200

2400, 1000, 2301

Synchronized with the overall long-term organizational strategy

Defined according to the maturity model used

Most visible to stakeholders

Low costs actions first

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.

700

720

784

570

Insourcing of test automation based on an offer from a local company ABC that has people who are specialists in system level capture-replay automation tools and they also do regular training courses in test automation methods and tools. They can then work closely with Vicki.

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.