Free Practice Questions for iSQI CTFL-001 Exam

Testers identify defects, developers locate and correct defects, testers confirm the correction has cleared the original defect

Developers identify defects, testers locate defects, developers correct and confirm the correction has cleared the original defect

Testers identify and locate defects, developers correct defects and confirm the correction has cleared the original defect

Developers identify, locate and correct defects, testers confirm the correction

has cleared the original defect

Spelling mistake on an error message

A potential infinite loop

Memory leakage

A variable set to the wrong value

Test planning is performed only once, at the beginning of the life cycle, andgenerates a Master Test Plan

Test planning is performed at the beginning of the life cycle and again at the beginning of test execution

Test planning is performed at the beginning of the life cycle and again at every test level

Test planning is performed continuously in all life cycle processes and activities

By detecting and removing all the defects in the delivered code and ensuring that all tests adhere to the quality standards set for the project

By measuring reliability of the software and ensuring that it is always above 99.99%

By identifying root causes of defects from past projects and using the lessons learned to improve processes and thus help to reduce the defect count

By detecting all deviations from coding good practice and ensuring that these are corrected

At the beginning of the project

As soon as requirements have been approved

As soon as the UAT specification has been drafted

At any time before UAT begins

No priority or severity assigned

Incident numbering is manual rather than automated

No mentioning of reproduceability

No classification on type of incident

Brainstorming

Inspections

Expert interviews

Independent assessments

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.

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.

Testing for performance problems

Hiring a contractor after a test analyst leaves the company

Arranging a back-up test environment in case the existing one fails during testing

Performing a project retrospective meeting using the test results after each increment