Skip to main content

Spike Testing

Spike Testing is the testing in which suddenly Test Team increase/decrease the load over the system by a varying number of users and then observing the behavior of the system. The Objective of this sudden increase of load to check weather performance will suffer, system get crash or it handled this sudden increase/decrease load.

This type of Testing needed for the web page in which the number of users suddenly increase or decrease then on that cases it is chances to break down the system so the test the performance of the system of unexpected traffic is called the Spike Testing. Spike Testing also called Data Volume Testing.

Consider a web application of any university who declared the result today. Number of users who accessing of the web page sometimes increase and sometime decrease so on this type of web pages need Spike Testing in which we can verified that on sudden increment or decrement how the system is performing. We can manage this like this if there is a validation that maximum 100 user can access that page one time and if more then 100 users access that page then it can show the message that web page is fully loaded or we can allow the user into the system but little bit decrease the performance of the system. 

Comments

Popular posts from this blog

What is API?

In general way, API (Application Programming Interface) is the intermediate software which is useful for two applications to communicate. API is the tool which is used for interaction of two applications. If developer developing any software which have multiple blocks (Modules) than developer use APIs to put them together.

Ad-Hoc Testing

Ad-Hoc Testing is the testing type which is performed without any proper procedure and without any Requirement Specification. Ad-Hoc testing is totally informal testing which have intension to break the application as early as possible and found important defect early.  In Ad-hoc testing tester do not have any test cases so only the users who have very high knowledge regarding the application only they can perform Ad-Hoc Testing.

Smoke Testing

In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.