CHAPTER 8 :-TESTING

Test Case Execution

The workflow diagram below depicts the high level steps necessary to follow in order to set up and execute test based on the Test Case Template.

Legend

1 - BII WG4 Test Case Template.doc. The Test Case template used to define and set up the Test Case Description.

2 – The test object specification provides a reference to the object subject to test or if required, enter a copy of the object description excerpted from the object description for the test object. When referenced, the reference should include at least :

SYSTEM TESTING:

System testing is the expensive and time-consuming process. There are two strategies for testing software that we use for testing our system: Code Testing and Specification Testing. In Code testing, we developed those cases to execute every instructions and path in the program. In specification testing, we examined the program specification and then wrote test data to determine how the program operates under specified condition..

We have tested each module separately i.e. have completed unit testing first and system testing was done after combining /linking all different Modules with different menus and thorough testing was done. Testing is a very important part of SDLC and takes approximately 50%of the time.

Once the system is a live one, Maintenance phase is important. Service after sale is a must and users/ clients must be helped after the system is implemented. If he/she faces any problem in using the system, one or two trained persons from developer’s side can be deputed at the client’s site, so as to avoid any problem and if any problem occurs immediate solution may be provided.

OVERVIEW OF TESTING:

Testing: Testing involves executing the program (or part of it) using sample data and inferring from the output whether the software performs correctly or not. This can be done either during module development (unit testing) or when several modules are combined (system testing).

Defect Testing: Defect testing is testing for situation where the program does not meet its fictional specification. Performance testing tests a system's performance or reliability under realistic loads. This may go some way to ensuring that the program meets its non-functional requirements.

Debugging: Debugging is a cycle of detection, location, repair and test. Debugging is a hypothesis testing process. When a bug is detected, the tester must form a hypothesis about the cause and location of the bug. Further examination of the execution of the program (possible including many returns of it) will usually take place to confirm the hypothesis. If the hypothesis is demonstrated to be incorrect, a new hypothesis must be formed. Debugging

tools that show the state of the program are useful for this, but inserting print statements is often the only approach. Experienced debuggers use their knowledge of common and/or obscure bugs to facilitate the hypothesis testing process. After fixing a bug, the system must be reset to ensure that the fix has worked and that no other bugs have been introduced. This is called regression testing. In principle, all tests should be performed again but this is often too expensive to do.

This site is designed to help BCA MCA student to develop final project and synopsis Download Free BCA Project, MCA Project, IT Projects, Final report and Project synopsis with Full documentation and code

Free download MCA projects in ASP.NET with documentation, Free download MCA projects in VB.NET with documentation, Free download MCA BSc CS projects in C#.NET with documentation,

Free download MCA projects in JAVA with documentation, Free download MCA projects in PHP with documentation, Free Download MCA BTech BE MSc BSc IT CS projects in PHP with MY SQL

Free Download BCA Final Year Project Synopsis, Free Download BCA Final Year Project Report, Free Download MCA Final Year Project Synopsis, Free Download MCA Final Year Project Report