This paper explains what are the different steps followed in Software Testing, how bugs are tracked and logged based on its Severity and Priority, what is the latest testing methodology and combinations of testing techniques applied to remove defects from the software and the different testing documents and formats required.
test cases are developed with an intension to demote the software that has been built.
Testing is considered to be destructive rather than constructive. However, the objective of
testing is constructive.
The goal of testing is to discover defects in a program, which means bug fixing of errors in the requirement analysis, design and coding phase of developing software. The primary goal is bug prevention and secondary goal is bug discovery. In software development activities, errors are introduced due to logical errors, careless or improper communication, and the need to rush through the whole process of software development. Testing is, therefore, conducted to uncover and reduce those errors.
satisfaction or not. The main purpose of testing is to discover defects in a program. When planning test, reporting the status of the defect and recommending actions, it is also important to have an understanding of the relative criticality of defects.
introduced due to logical or syntactical faults. Bugs can be software bug or hardware bug. Some bugs may be deferred or postponed for fixing or locking in subsequent release of the next version of the software. These bugs are called \u2018The Deferred Bugs\u2019.
not behave as expected. Debugging is an activity, which supports testing but cannot replace them. No amount of testing is said to be sufficient to grantee a hundred percent error free software.
Smoke Testing / Sanity Testing / Gorilla Testing / Qualification Testing\ue000 Ad-hoc Testing\ue000 Write test cases from Functional Requirement Specification (FRS)\ue000 Executing test cases manually (Module Testing)\ue000 Logging / Reporting Bugs through Bug Tracking life cycle\ue000 Regression testing done to ensure stable position of software
In Smoke testing each time the test team receives a new version of the program, an initial test is performed to determine whether the built is stable enough to be tested. It is a short test hitting all the major pieces of functionality i.e. \u201cA shot through the dark\u201d, to determine if the software is performing well enough to be accepted for major testing efforts.
need not be documented by the testing team. Tests are random and are based on error guessing ability, knowledge of the business process. The test includes initial and later steps in testing. A program may pass at the first time but may fail for the second time.
Regression testing is done when a change is made to the source code and a new module is added. A set of predefined test cases has to be checked to determine whether any other portions of the software are affected or not.
InIntegrat ion testing the combined parts of the application are tested to determine if they together function correctly or not. They can be units, modules and their interfaces, individual applications, clients or servers.
This action might not be possible to undo. Are you sure you want to continue?