ISTQB Foundation Level Exam Crash Course Part-26
This is Part 26 of 35 containing 5 Questions (Q. 126 to 130) with detailed explanation as expected in ISTQB Foundation Level Exam Latest Syllabus updated in 2011
Deep study of these 175 questions shall be of great help in getting success in ISTQB Foundation Level Exam
Q. 126: What is the short cut method to remember all 16 sections of a test plan as described in IEEE 829?
A useful revision aid to help remember the 16 sections of the IEEE 829 test plan is the acronym �SPACEDIRT�. Here each letter refers to one or many sections of the test plan as described below:
S – Scope (including test items, features to be tested and features not to be tested)
P – People (including responsibilities, staff and training and approvals)
A – Approach
C
– Criteria (including item pass/fail criteria and suspension and resumption requirements)E – Environment needs
D – Deliverables (test)
I – Identifier and introduction (test plan)
R – Risks and contingencies
T – Testing tasks and schedule
<<<<<< =================== >>>>>>
Q. 127: What are the different Activities involved in Test-Planning?
During test planning various activities for an entire system or a part of a system have to be undertaken by those working on the plan. These activities are:
1) Working with the project manager and subject matter experts’ to determine the scope and the risks that need to be tested. As well identifying and agreeing the objectives of the testing, be they time, quality or cost focussed, or in fact maybe a mixture of all three. The objectives will enable the test project to know when it has finished.
2) Putting together the overall approach of testing (sometimes called the test strategy), ensuring that the test levels and entry and exit criteria are defined.
3) Liaison with the project manager and making sure that the testing activities have been included within the software life-cycle activities such as:
a) Design – The development of the software design;
b) Development � The building of the code;
c) Implementation – The activities surrounding implementation into a live environment.
4) Working with the project to decide what needs to be tested, what roles are involved and who will perform the test activities, planning when and how the test activities should be done, deciding how the test results will be evaluated, and defining when to stop testing (exit criteria).
5) Building a plan that identifies when and who will undertake the test analysis and design activities. In addition to the analysis and design activities test planning should also document the schedule for test implementation, execution and evaluation.
6) Finding and assigning resources for the different activities that have been defined.
7) Deciding what the documentation for the test project will be, e.g. which plans, how the test cases will be documented, etc.
8) Defining the management information, including the metrics required and putting in place the processes to monitor and control test preparation and execution, defect resolution and risk issues.
9) Ensuring that the test documentation generates repeatable test assets, e.g. test cases.
<<<<<< =================== >>>>>>
Q. 128: What are the different Exit Criteria for the test execution?
Entry criteria are used to determine when a given test activity can start. This could include the beginning of a level of testing, when test design and/or when test execution is ready to start.
Examples of some typical entry criteria to test execution include:
1) Test environment available and ready for use (it functions).
2) Test tools installed in the environment are ready for use.
3) Testable code is available.
4) All test data is available and correct.
5) All test design activity has completed.
<<<<<< =================== >>>>>>
Q. 129: What are the different Entry Criteria for the test execution?
Exit criteria are used to determine when a given test activity has been completed or when it should stop. Exit criteria can be defined for all of the test activities, such as planning, specification and execution as a whole, or to a specific test level for test specification as well as execution.
Exit criteria should be included in the relevant test plans.
Some typical exit criteria are:
1) All tests planned have been run.
2) A certain level of requirements coverage has been achieved.
3) No high-priority or severe defects are left outstanding.
4) All high-risk areas have been fully tested, with only minor residual risks left outstanding.
5) Cost�when the budget has been spent.
The schedule has been achieved, e.g. the release date has been reached and the product has to go live.
Exit criteria should have been agreed as early as possible in the life cycle; however, they can be and often are subject to controlled change as the detail of the project becomes better understood and therefore the ability to meet the criteria is better understood by those responsible for delivery.
<<<<<< =================== >>>>>>
Q. 130: What is Metrics-Based Approach of Test Estimation?
Metrics based approach relies upon data collected from previous or similar projects.
This kind of data can include the following:
1) The number of test conditions.
2) The number of test cases written.
3) The number of test cases executed.
4) The time taken to develop test cases.
5) The time taken to run test cases.
6) The number of defects found.
7) The number of environment outages and how long on average each one lasted.
With this approach and data it is possible to estimate quite accurately what the cost and time required for a similar project would be.
It is important that the actual costs and time for testing are accurately recorded. These can then be used to revalidate and possibly update the metrics for use on the next similar project.
Part – 27 of the Crash Course – ISTQB Foundation Exam
Access The Full Database of Crash Course Questions for ISTQB Foundation Level Certification
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.