Page 31 - SOFTWARE TESTING & QUALITY ASSURANCE

Software Testing and Quality Assurance

2.5 Summary

• Testing strategies and techniques help the tester to carry out the test efficiently to find maximum
number of bugs in software.
• A static test is carried out to check for bugs in software before the software is compiled and run. A
dynamic test is carried out after the software is compiled and executed.

• Manual test involves performing the test without taking the support of any testing tools. All the
test activities such as writing the test case, providing the inputs, recording the output and
comparing the expected and obtained output are carried out by the testers manually.
• Automated testing is completely dependent on software testing tools. The tester writes the test
cases and the tools perform the test activities.
• A good software tester must be creative, explorative and should be able to identify the ideal
process involved for testing and realize the impact of bugs on a project.
• Structural testing techniques check the occurrence of bugs in the test software using the actual
codes of the software. The tester works with the source code of the software while performing the
test.
• In a functional test, the tester is not aware of the actual working of the software. The test analysis
is performed based on the outputs that the software generates for various inputs. The bugs are
detected by comparing the expected output with the obtained output.
• Software axioms are self-evident facts which bring to light the real-life situations faced by testers.
2.6 Keywords

Axioms: Axioms are postulates which are accepted on their own merits without any mathematical rule.
They require no proof. They are formulas that are not derived from others but are self-evident facts.
SWEBOK: Software Engineering Body Of knowledge is a product of the Software Engineering
Coordinating Committee which is sponsored by the IEEE Computer Society. They define knowledge
areas within software engineering. This includes Software requirements, Software design, Software
construction, Software testing, and Software maintenance.

Test Strategy: Test Strategy is an outline that describes the testing aspects to the respective
stakeholders. The Stake holders could be project managers, testers, and developers. Test strategy
discusses the team’s approach to the testing process.
Testing Tool: Automation of tests is carried out with the help of a testing tool. The tool is software
which controls the execution of tests. The software compares the actual and predicted outcomes, the
setting up of test conditions and the test control and test reporting functions.
2.7 Self Assessment

1. State whether the following statements are true or false:
(a) The test strategy views the test event at high level, concentrates on the objectives of the test
event, the techniques that can be used and the resources that are required.
(b) During the process of automation testing, the possibility of recurrence of a bug several
times can actually have an impact on the time taken for testing the software.
(c) In white box testing, as the tester has the knowledge of internal coding, it is very easy to
develop test cases to test the software effectively.
(d) While performing a software test, the tester should first begin the test with test to fail and
check whether the software works fine without any bugs.
(e) The tester enters erratic or irrelevant data and checks the response of the software while
performing mutation testing.

24 LOVELY PROFESSIONAL UNIVERSITY