Page 290 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING
P. 290
Principles of Software Engineering
Notes Testing Tools and Automation: You should have information about what tools you are using to
manage your testing activities. You should have information on the configuration management for
test artifacts, test case management tool, defect tracking system, tools for automation etc. Ideally,
test automation should be treated as separate project and you should have brief information
here along with the link to automation plan.
It is also be described as a detail of how the testing will proceed, who will do the testing, what
will be tested, in how much time the test will take place, and to what quality level the test will
be performed.
Test plan is a document which includes introduction, assumptions, list of test cases, and list of
features to be tested, approach, deliverables, resources, risks and scheduling.
A test plan is a systematic approach to testing a system such as a machine or software. The plan
typically contains a detailed understanding of what the eventual workflow will be.
Detecting all of the different failure modes for software is generally infeasible.
Self Assessment Questions
1. Among the more common errors in computation are:
(a) Comparison of different data types
(b) Precision inaccuracy
(c) Incorrect logical operators or precedence
(d) Incorrect comparison of variables
2. Integration testing is a systematic technique for constructing the program true while at
the same time conducting tests to uncover errors associated with facing.
(a) System testing (b) Unit testing
(c) Integration testing (d) None of these
3. The ..................... strategy verifies major control or decision points early in the test process.
(a) regression (b) bottom-up integration
(c) smoke (d) top-down integration
4. A classic ........................ problem is finger-pointing.
(a) recovery testing (b) system testing
(c) security testing (d) stress testing
5. Test plan is a document which includes, introduction, assumptions, list of test cases, list
of features to be tested, approach, deliverables, resources, risks and scheduling.
(a) True (b) False
14.3 Test Case Specifications
Test cases are designed by the stepwise elaboration and refinement of the identified test conditions
using test techniques identified in the test strategy. They should be repeatable, verifiable and
noticeable back to requirements.
Test case design includes the identification of:
• The preconditions such as either project or localized test environment requirements and
the plans for their delivery
• The test data requirements
• The expected results and post conditions.
284 LOVELY PROFESSIONAL UNIVERSITY