Following are the Test processes we would follow:

1. Understanding the application to be tested
2. Defining the workflow of each module
3. Device test cases for each form/screen
4. Functional Testing of the application to confirm on the workflow and test cases defined
5. Undertake Performance Testing
6. Stress Testing
7. Load Testing

Performance Testing

The goal of performance testing is not to find bugs, but to eliminate bottlenecks and establish a baseline for future regression testing.

Step 1. Identify Desired Performance Characteristics
Step 2. Identify the Test Environment
Step 3. Create Test Scripts
Step 4. Identify Metrics of Interest
Step 5. Create Performance Tests
Step 6. Execute Tests
Step 7. Analyze Results, Report, and Retest

The most common reasons for conducting performance testing can be summarized as follows:

1. To ensure fast response times for end-users
2. To ensure the system can handle production traffic and not crash
3. To ensure the application doesn’t over-utilize system resources like CPU, or RAM.
4. To ensure the system can handle more and more users, over time.
5. To ensure the application is free from limits and bottlenecks
6. To determine how much hardware and what kind of hardware to use
7. To ensure different system configurations or architectures will work in production

Stress Testing

Stress testing tries to break the system under test by overwhelming its resources or by taking resources away from it (in which case it is sometimes called negative testing). The main purpose behind this madness is to make sure that the system fails and recovers gracefully -- this quality is known as recoverability.

Load Testing

In the testing literature, the term "load testing" is usually defined as the process of exercising the system under test by feeding it the largest tasks it can operate with.