THE NEW KCSE PROJECT GUIDELINES PART 10: SYSTEM TESTING

​THE SYSTEM TESTING (THE NEW KCSE PROJECT GUIDELINES)

System testing also called ​bench marking, is the process of executing a program with a purpose of check errors or simply debugging.
System testing is necessary because it carries out all the intended functions within the underlayed limits and also it is an on going activity throughout design and construction of the system. 

Testing is done by input a set of values, and comparing the expected results with the actual ones. The level of correctness required depends on how critical the application is.

stages of system testing

there are several stages of testing a system namely:

1. desk checking (dry run)
   Desk checking is an informal manual test that programmers can use to verify coding and algorithm logic before a program launch. This enables them to spot errors that might prevent a program from working as it should.
   
2. compiler or assembler system checking
   this involves checking whether translators are working properly.
   
3. program run with test data
   involves appending sample data to the tables check for the expected output.
   
4. diagnostic procedures
   A diagnostic procedure is an examination to identify a system's specific areas of weakness and strength in order determine on what areas to improve.
   
5. full scale testing with actual data
   new programs are run in parallel with the existing system for a short time so that results can be compared and adjustments made. This is done with actual data.

In the evaluation KCSE examinations, system testing is captured in the marking scheme as 'demonstration by the candidate' and marks are spread accordingly as shown by this KCSE 2010 project marking guidelines below.

Because most students use DBMS to construct the system, it is advisable that they append at-least 10 records in the  database to test whether their systems are working properly and giving out expected outputs. 

SYSTEM TESTING AS CAPTURED BY KCSE 2010 MARKING SCHEME

However, latest marking schemes do not include this part and therefore carry zero marks. This marks have been redistributed to other marking indicators.

Why are systems tested?

1. Remove errors (debugging)
2. Whether they give out the expected output and expectations.
3. Determining the accuracy of the system.
4. To find out the performance under different conditions to determine the capabilities of the system.
5. To determine the effectiveness and efficiency of the system before it is implemented.

<<< PREVIOUSLY

THE NEW KCSE PROJECT GUIDELINES PART 11: SYSTEM USER MANUAL