Types of Software Testing, Smoke Testing, Static Testing, Scenario Testing, Sanity Testing




  1. Smoke Testing: This functionality is done to confirm the basic functionality of system immediately after the system developed. This testing generally done by Testing Team..
  2. Stability Testing: This testing confirms that when and in which condition application will crash, how much application is stable for specific types of works. This type of testing generally performed by Performance engineers.
  3. Static Testing: Only testing the document, algorithm or sanity of code is called static testing. Actually In this testing software isn’t used. This testing is done by Software developers.
  4. Statement Testing: It is a part of white box testing; this testing performs by the development team. Statement provided in code should be executed once during application testing and should satisfy the required expectations.
  5. Scalability Testing: Generally this testing is performed by the performance engineers. This testing used to measure the capability to scale up the application mean user load supported, the data volume, the number of transactions etc.
  6. Scenario Testing: This testing is also performed by the testing team. Scenarios are the already explained hypothetical story to help the test engineers think through system or difficult hitch for a testing environment.
  7. Sanity Testing: This testing process is used to confirm the performance of newly version of application. This performance should be well enough for acceptance. This testing usually done by the Test engineers.
  8. Security Testing: This testing confirms that highly private or confidential data is properly secured and that can not be hacked by any way. This testing performed by the Test Engineers or the specialized security – testing companies.
  9. Requirement Testing: This testing verifies the correctness, completeness, unambiguously and logically consistent and necessary designing is completed properly and working fine. This testing is done by the QA Team.
  10. Recovery Testing: This testing confirm the system capability of recovery mean when system crashes or its any hardware get failed then can it recover and if yes then how much time it will take to recover. This testing is done by Testing engineers.
  11. Regression Testing: This testing is done after the new changes have been made in software or previous bus has been fixed. Regression testing is used to confirm the side effects of recently made changes. This testing always performed by the Testing Engineers.
  12. Ramp Testing: This testing will check the limit of break down of system mean after how much input signal continuously system will get break down. This testing can be done by performance engineers or the Test engineers.
  13. Qualification Testing: This testing qualifies the software. Software Qualification is depend only on requirement provided by client and its performance, So if the developed application is satisfied the client requirement and it performance requirement then it will be qualified for live. This testing is done by the Testing engineers.
  14. Performance Testing: When any application will pass with some specified performance requirements then this testing will called the performance testing. This testing is done by the performance engineers.
  15. Penetration Testing: Testing scenarios which evaluate the security of any application or software or attack from a nasty source. This testing usually performed by the specialized testing companies of penetration.


No comments:

Post a Comment

Popular Posts