Software Engineering Testing
Software Engineering Testing
Testing
Testing
No program or system design is perfect communication between the user and the designer is not always complete or clear and time is also short the result is errors
In a new design system should have all the piece in working order, but in reality each piece work independently. now is the time to put all pieces in one system and test it to determine whether it meets the user requirement
Copyright BCA Notes All Rights Reserved.
Unit testing: testing change made in the existing or new program Sequential or series testing is checking the logic of one or more programs in candidate system ,where output of one program will affect he processing done by another program System testing: is executing a program to check logic change made in it with intension of finding errors Positive testing : making sure that new programs do in fact processes certain transaction according to specification Acceptance testing : running the system with live data by the actual user
Copyright BCA Notes All Rights Reserved.
The first test of a system is to see whether it produces the correct output
Online response : online system must have a response time that will not cause hardship to the user e.g. input transactions in as many CRT screen as would normally be used in peak hours and time the response to each online function Volume : we create as many records as would normally be produced to verify that hardware and software will function correctly user is asked to provide test data Stress testing : is to check that candidate system does not malfunction under peak loads i.e. high volume of data over a short time Recovery and security: a forced system failure to test a backup recovery procedure for file integrity, inaccurate data are entered to see how the system responds in terms of error detection and protection and demonstrate data and programs are secure from unauthorized access Usability documentation and procedure: the usability test verifies the user friendly nature of the system it relates to normal operating and error handling procedure e.g. accurate and complete documentation
Copyright BCA Notes All Rights Reserved.
A checklist is useful for user training The training plan is followed by user training manuals and other text materials Facility requirement and necessary hardware are specified and documented A common procedure is to train supervisor and department heads who in turn train their staff as they see fit for the following reasons
Supervisor are knowledgeable about the capabilities of staff and overall operations Staff members respond more favorably from supervisors then outsiders Familiarity of users with their particular problem (bugs) make them better candidates for handling user training than the system analyst. The analyst get feed back to ensure that proper training is provided.
Copyright BCA Notes All Rights Reserved.
All programs have to be compiled /assembled for testing Before this , a complete program description should be available . included is purpose of program , it use , the programmer who prepared it and amount of computer time it takes to run it . Program and system flowchart of the project should also be available for reference. In addition to these activities , desk checking the source code uncover programming errors. Before actual program testing , a run order schedule and test schemes are finalized A run order schedule specifies the transaction to test and the order in which they should be tested High priority transactions that make special demand on the candidate system are tested first Test scheme specifies how program software should be debugged A common approach called bottom up programming tests small scale program modules which are linked to a higher level module and so on until program is completed
Copyright BCA Notes All Rights Reserved.
Compile/assemble programs