Testing Type U I S UAT

U I S UAT - Unit, Integration, System, User Acceptance Testing.

 What is System Testing?

System Testing is the testing of a complete and fully integrated software product. Usually software is only one element of a larger computer based system. Ultimately, software is interfaced with other software/hardware systems.System Testing is actually a series of different tests whose sole purpose is to exercise the full computer based system.

Two Category of Software Testing

1. Black Box Testing
2. White Box Testing

System Testing involves testing the software code for following

• Testing the fully integrated applications  including external peripherals in order to check how components interact with one another and with the system as a whole. This is also called End to End testing scenario..
• Verify thorough testing of every input in the application to check for desired outputs.
• Testing of the user's experience with the application.

Software Testing Hierarchy

1. Unit testing - testing performed on each module or block of code during development. Unit Testing is normally done by the programmer who writes the code.


2. Integration testing - testing done before, during and after integration of a new module into the main software package. This involves testing of each individual code module. One piece of software can contain several modules which are often created by several different programmers. It is crucial to test each module's effect on the entire program model.


3. System testing - testing done by a professional testing agent on the completed software product before it is introduced to the market.


4. Acceptance / UAT testing - beta testing of the product done by the actual end users.

Different Types of System Testing

1. Usability Testing  - Usability Testing mainly focuses on the user's ease to use the application, flexibility in handling controls and ability of the system to meet its objectives


2. Load Testing - Load Testing is necessary to know that a software solution will perform under real-life loads.


3. Regression Testing- - Regression Testing involves testing done to make sure none of the changes made over the course of the development process have caused new bugs. It also makes sure no old bugs appear from the addition of new software modules over time.


4. Recovery Testing - Recovery testing is done to demonstrate a software solution is reliable, trustworthy and can successfully recoup from possible crashes.


5. Migration Testing - Migration testing is done to ensure that the software can be moved from older system infrastructures to current system infrastructures without any issues.


6. Functional Testing - Also known as functional completeness testing, Functional Testinginvolves trying to think of any possible missing functions. Testers might make a list of additional functionalities that a product could have to improve it during functional testing.


7. Hardware/Software Testing - IBM refers to Hardware/Software testing as "HW/SW Testing". This is when the tester focuses his/her attention on the interactions between the hardware and software during system testing.

What Types of System Testing Should Testers Use?

1. Who the tester works for 
2. Time available for testing
3. Resources available to the tester 
4. Software Tester's Education 
5. Testing Budget