![Page 1: Software Testing. Introduction Testing is often left to the end of the project which is generally not a good idea. Testing should be conducted throughout](https://reader036.vdocument.in/reader036/viewer/2022082817/56649e2f5503460f94b1ff76/html5/thumbnails/1.jpg)
Software Testing
![Page 2: Software Testing. Introduction Testing is often left to the end of the project which is generally not a good idea. Testing should be conducted throughout](https://reader036.vdocument.in/reader036/viewer/2022082817/56649e2f5503460f94b1ff76/html5/thumbnails/2.jpg)
Introduction Testing is often left to the end of the
project which is generally not a good idea. Testing should be conducted throughout
the project. A testing plan should be created at the
beginning of the project and continuously updated during the duration of the project.
At different stages of testing all parts of the system will not be complete, hence stubs my need to be written for these parts.
![Page 3: Software Testing. Introduction Testing is often left to the end of the project which is generally not a good idea. Testing should be conducted throughout](https://reader036.vdocument.in/reader036/viewer/2022082817/56649e2f5503460f94b1ff76/html5/thumbnails/3.jpg)
Stages of Testing
Unit testing Integration testing System testing Acceptance testing
![Page 4: Software Testing. Introduction Testing is often left to the end of the project which is generally not a good idea. Testing should be conducted throughout](https://reader036.vdocument.in/reader036/viewer/2022082817/56649e2f5503460f94b1ff76/html5/thumbnails/4.jpg)
Unit Testing There are approaches to unit testing,
namely, black-box testing and white-box testing.
In black-box testing the tester examines whether each class meets its requirements, i.e. the class is treated as a “black-box”.
White-box testing on the other hand, looks at the code in the class to identify errors.
The default approach is black-box testing, unless the complexity of the program is high in which case white-box testing is used.
![Page 5: Software Testing. Introduction Testing is often left to the end of the project which is generally not a good idea. Testing should be conducted throughout](https://reader036.vdocument.in/reader036/viewer/2022082817/56649e2f5503460f94b1ff76/html5/thumbnails/5.jpg)
Integration Testing The main of this phase is to test the user interface. The tester moves through each menu in a top-down
manner. The use cases are also tested against the menu to
ensure that the requirements are met. This phase also involves interaction testing which
adds on a class and tests it. If the class meets the requirements the next class is
added and so on until the entire system is developed. This testing is then taken from the class to the
package level. If the system exchanges data with other systems this
is also tested during this phase. Test data is used in conducting these tests.
![Page 6: Software Testing. Introduction Testing is often left to the end of the project which is generally not a good idea. Testing should be conducted throughout](https://reader036.vdocument.in/reader036/viewer/2022082817/56649e2f5503460f94b1ff76/html5/thumbnails/6.jpg)
System Testing
Requirements testing Usability testing Security testing Performance testing Documentation testing
![Page 7: Software Testing. Introduction Testing is often left to the end of the project which is generally not a good idea. Testing should be conducted throughout](https://reader036.vdocument.in/reader036/viewer/2022082817/56649e2f5503460f94b1ff76/html5/thumbnails/7.jpg)
Acceptance Testing
The testing is done in two phases, namely, alpha testing and beta testing.
Alpha testing involves use of the system by the users to ensure that they accept the system.
Beta testing uses real data and not test data to identify system errors.