System Testing

 System Testing

After completion of Integration Testing, and receiving the build from development team, the testing team will concentrate on system testing to conduct using Black Box Testing techniques.

System Testing is divided into 3 sub stages.

1. Usability Testing.

2. Functional Testing

3. Non-Functional Testing.

Usability Testing

After receiving software build from development team, the testing team will conduct usability testing. In this test the testing team will estimate “User Friendly ness” of all screens in the software build. There are two sub tests.

User Interface Testing or UI Testing

In this test, the testing team will apply below 3 factors on every screen of the software build.

· Ease of use: To estimate understandability of screen.

· Look and Feel: To estimate attractiveness of screen.

· Speed in Interface: To estimate length of navigation as short.

Manual Support Testing

During this test the testing team will validate the correctness and completeness of help documents. These help documents are also known as User Manuals.

Case Study:

Functional Testing

It is a mandatory testing level in testing team responsibilities. During this test, testing team will concentrate on “Meet customer Requirements” through below sub tests.

a. Requirement Testing.

b. Sanitation Testing.

Requirements Testing

It is also known as Functionality Testing. During this test the responsible testing team will apply different coverage techniques as discussed below on the functionalities of software build.

· GUI Coverage / Behavioral Coverage: Changes in properties of objects in screens while operating.

· Error Handling Coverage: To prevent wrong operation on screens.

· Input Domain Coverage: Testing correct type and size of input values

· Manipulations Coverage: Returning correct output values.

· Back End Coverage: Valid impact of screens operations on back end data base tables.

· Functionalities Order Coverage: The arrangements of screens in the software build with respect to order of functionalities.

Sanitation Testing

During this test the testing team will concentrate on extra functionalities with respect to requirements of the customer. This testing is also known as garbage testing.

Non-Functional Testing

After completion of user interface and functional testing, the testing team will concentrate on Non-Functional Testing to validate quality characteristics of software build Like Security and Performance.

Recovery Testing

This testing is also known as Reliability Testing. During this test, the testing team will validate that whether the software build is changing from abnormal state to normal state.

Compatibility Testing

It is also known as Portability Testing. During this test, the testing team will validate that whether the software build is running on the customer expected platforms or not?.

Configuration Testing

It is also known as hardware compatibility testing. During this test the testing team will validate that whether the software build is supporting different technology hardware devices or not?

Example: Different technology printers.

Different topology networks, etc….

Inter Systems Testing

It is also known as End-to-End Testing. During this test the testing team will validate that whether the software build co-exists with other software applications to share common resources.

Example: Sharing data, sharing hardware devices, printers, speakers, sharing memory, etc….

Installation Testing

During this test, the testing team will establish customer site like configured environment. The testing team is practice installation of software build in to that environment.

3.6.3.6 Load Testing

The execution of the software build under customer expected configuration and customer expected load to estimate speed of processing is called as load testing. Here, load means that the no of concurrent users working on the software. This is also known as scalability testing.

3.6.3.7 Stress Testing

The execution of the software build under customer expected configuration and various load levels from low to peak is called stress testing. In this testing, testing team will concentrate on load handling by the software build.

3.6.3.8 Storage Testing

Testing whether the system meets its specified storage objectives.

Testing the data of different formats and in different devices. Verifying the efficiency of data storage in devices and proper retrieval of the data.

3.6.3.9 Data Volume Testing

Volume testing refers to testing a software application with a certain amount of data. This amount can, in generic terms, be the database size or it could also be the size of an interface file that is the subject of volume testing. For example, if you want to volume test your application with a specific database size, you will expand your database to that size and then test the application’s performance on it.

Example: MS Access technology support 2GB of database as maximum.

3.6.3.10 Parallel Testing

It is also known as Comparative Testing. During this test, the testing team will compare the software build with other competitive software in market or with old version of same software build to estimate completeness. This is applicable only for software product but not on software applications.