different types of testing

Different Types of Testing:

Smoke test:
Smoke test is conducted before conducting performance test to find out whether the application runs smoothly under basic load. This is mainly to find out whether the application runs as desired functionally. i.e to check if each and every component of the product works well.Performance testingPerformance test is normally done to validate/investigate the performance of the application in terms of its speed (response time), and other characteristics like through put, of the application under test.

Load testing:

Load testing is done to find out the application / product behavior under peak load situations. Load testing is done to know whether the product meets the expected requirements as mentions in production base lines or as represented in SLA (service level agreement). Load testing is done to know up to what load system can handle with out failure. It is assumed that below that level system fails for any further requests/load.

Stress testing:

Stress testing is a subset of Load testing where it is also done to see the performance of the application under peak loads. But here the load is applied to such extent that the system completely crashes and will not respond to any requests. The load will be applied continuously until the system fails. These metrics also used for future reference when the load increases in future.Capacity testingCapacity testing is done to find out the measurements of the servers in terms of CPU utilization, memory usage, other server resources etc… This is mainly to determine the health of the environment, not the application. Environment means the servers where the application is installed and other tools that that are used to distribute the loads to the servers and the servers that run the application etc…

Spike testing:

Spike testing is similar to stress testing. In spike testing load is applied beyond its peak load point at frequent intervals in a zigzag way to find out the applications performance.Endurance testingEndurance testing is done for long hours to check if the application works well in a consistent manner for long duration of runs. When a test is run for long hours normal errors may found is Garbage collection , memory leakage etc..

Unit testing:

Unit testing is done normally for a single peace of code out of the whole application. Normally unit testing is conducted by developers when they finished their coding for the assigned unit. Developers will prepare their own test cases and do the unit testing.

Different types of performance risks:

The typical risks involved while doing performance testing includes:
Application speed Risks, Scalability Risks, Stability risks.

Application Speed risks:

Application Speed risks can be defined in this way.Check whether the application is responding with enough speed so that the end users are satisfied with its response time.Check if the application in enough fast to process the data on time. For example if a customer request data needs to be processed with in 1 hour after submission, but the application takes 1.3 hrs?Check if the application gives updated and accurate data every time when needed? I.e. data related to share quotes, flight timings, currency values etc..To avoid the above mentioned speed related risks make sure you take the below precautions before releasing the product.Compare the finished application/product with the existing competitors product and see if your product speed is more than or equal to that.Compare your application’s speed with the older versions of the same applications to check if the new built is faster than the old version.Conduct performance testing parallel to some downloads, uploads from and to the application or while some virus scanning is going on.Conduct performance testing by putting heavy loads on the application just as in real time.Know the feed back of the application end users about your application.Scalability Risks:Scalability Risks include the below.Check whether the application performs as desired under peak load and at maximum loads at peak hours.Check if the application can process all the data under peak loads applied to it.Check if the application functionality is as desired even when heavy loads applied.Stability Risks: