Know more about System Testing- What is System Testing?

What is System Testing?

            System Testing is Performed on the entire system in the context of a Functional Requirement specification.System testing is done after unit,component and integration testing.It is defined as a testing phase conducted on the complete integrated system,to evaluate the system compliance with its   Specified requirements.

What is System Testing?

Overview of System Testing :

• A System is a complete set of integrated components that together deliver product functionality and features.System testing will find the issues from basic like design,architecture and code of the whole product.
• It will test the functional and non-functional aspect of the product.
• Functional side system testing focus on a real life customer usage of the product and solutions mostly it implemented like insurance,banking etc.... 
• On the non-functional side it has different types of testing they are:  

                     1. Load Testing
                   
                     2. Scalability testing
                   
                     3. Reliability Testing

                     4. Stress Testing

                     5. Interoperability Testing

                     6. Localization Testing

• Mostly system testing is done based on test cases the system test cases are created by collecting  the information from detailed design documents,module specification and system requirement specifications.
• System testing will start after the completion of unit,component and integration testing because they would test the basic errors and defects.

Why are we doing System Testing?

• System testing helps to identify the defects before the product is ready for delivery.It is the last phase of testing before the product release it won't fix all defects in a code due to time constrain  and effort needed in development.If customer found any defect then defect will be fixed before release.
• Mainly the system testing helps to reduce the risk of releasing a product.

• It has independent approach in testing.

• They have customer view in testing.

• It discover defect which are not found in earlier testing.

• It test both functional and non functional aspects of product.

• It will reduce the risk before the product is ready for acceptance testing.

System Testing

 Functional System Testing :

• Functional testing will happen in various testing phases they are two problems.
• Duplication
• Gray area
• The same test will do for multiple times is known as Duplication.In  Gray area the certain test are missed out in all the phases.
• It happens due to lack of product knowledge,lack of knowledge of customer usage and co-ordination across test teams.
• The some of the common techniques are:

1. Design/architecture verification
2. Vertical Testing
3. Deployment Testing
4. Beta Testing
5. Certification,standards, and testing for compliance.

1. Design/architecture Verification :

• In functional testing the test cases are developed and verify against the design and architecture to see whether they are actual product level test cases. Mostly functional system test cases focus on behaviour of complete product.
• It helps to validate the product features based on customer scenarios and verify them using product implementation.Mostly in functional testing they reject the test cases and move them to earlier phases to find defect and avoid major defects.

2. Business Vertical Testing :

Testing the product for different business verticals such as insurance,banking,asset management and so on, and verifying the business operations and usage is called business vertical testing.

• Business vertical testing can be done in two ways that is simulation and replication.
• simulation in vertical testing, the customer or the tester assumes the requirement to test the business flow.
• In replication the product is completely customised and customised product get tested and is released to the customer.

3. Deployment Testing :

• Deployment testing is a type of production testing which is performed after the code is deployed to check whether it is working fine in production or not.
• Deployment testing happens in two ways onsite deployment and offsite deployment.
• Deployment testing is also conducted after the release of the product by utilizing the resources and setup available in customer's locations.This is a combined effort by the product development organization and the organization trying to use the product.This is called onsite deployment.
• Testing happens in a product development company to ensure that customer deployment requirements are met is called offsite deployment.

4. Beta Testing :

• It used to test the basic functionality of an application.One of the mechanism of beta testing is used to test the product by customer and receive the feedback is called beta testing.
• During entire duration of beta testing the various activities are performed and executed according to an specific schedule is called beta program.

5. Certification,Standard and Testing for Compliance :

• Before the product release the product need to be certified.The certification agencies give certification for the product they will see whether they used popular hardware,operating system,database and other infrastructure pieces.This is know as certification testing.
• In the beginning of the project itself they need to select the standards to be implemented.There are so many standards but not all standards are possible because some are non-functional issues.so we need to ensure these standards are properly implemented is called testing for standards. 
• Testing the product for Contractual,legal and statutory compliance is one of the critical activities of the system testing.

Non-Functional Testing :

The non-functional testing is similar to functional testing the only difference is complexity,knowledge requirement,effort needed and number of times the test cases are repeated.

The Non-functional testing need more robust stronger than functional testing to reduce the repetition. 

They have better planning to overcome the repetition that are:

1. Setting up the configuration
2. Entry/Exit criteria
3. Balancing key resources
4. Scalability Testing
5. Reliability Testing
6. Stress Testing
7. Interoperability Testing