top of page
Test Harness

This used for software testing in which the software is automatically tested with test data and then the developer can sort out any errors found. This is useful because it saves time and the qulaity of the software afterwards is better

 

Perfomance testing

This is used to determine how fast a system or part of a system can work under a defined workload. This can show that the system meets a certan criteria and it can compare two systems to see which does better or at what workload a  system fails or begins to produce lower quality.

 

Scalability testing

This is used to test that the application can work under certain work loads.

 

Volume Testing

This tests that a system can handle values that may become larger over time i.e. data files and logs.

 

Usability Testing

This checks how well people can use the system or part of it. For example the use of a webpage. 

 

Multiplatform testing

As the name suggests it check if the system can be used with different hardware or software.

 

Other types of testing include:

 

Prototyping - This is when a prototype of each stage of developement is produced for users to test. It is helpful because it allows the system to be tailored to the users needs instead of leaving it to the end becaus ethere may be too many changes to go back and implement them.

 

Paper Prototype testing - This is when the system is made on paper and the developer and the user sit down and try to perform tasks with the paper version of the system. This allows for the immediate assement of how the user interacts with the system and difficulties that should be corrected.

 

Simulated enviroments - This simulates a real life usage of the system. For example it is hard to test a website that would hve thousands of users using it at once without the thousands of users, therefore the simulated environment test would simulate the thousands of users allowing for accurate testing and results.

Introduction and Recording Techniques

Techniques for Testing

Before the analysis of the system can begin it is necessary to find out information concerning the system. There are a number of different ways information can be found out:

 

Interviews - This is usually conduted with a manager (strategic level) as the interviewee because they have an overview of how the whole system should work. An operarional staff would only be able to give fine detial about their area of work.

 

Observation - The best way to learn if you are required to take a position in a company is through observing what they are doing on the job.

 

Inspection of Records - Examination of documents of the company helps to understand what information is held and how it is communicated or transferred between departments. These documents could include: staff CVs, Job descirptions, poilcy manuals and previous system documentatiions.

 

Questionnaires - Questionnaires are a good way of gathering a lot of information quickly as it is tailored to the way you want it and you are not required to be there when it is fill out. Unfortunately, this method comes with some disavantages as well i.e. many forget to fill them in and respondents may misunderstand the questions. Both of these reasons may result in an incomplete picture of the system.

bottom of page