Types of Performance Testing

Performance Testing Types :

P.T = L.E.S.S

Performance Testing = Load, Endurance, Stress, Spike

So, there are four types of P.T mentioned above.

Testing Outline Analysis

Testing Outline Analysis :--

The objective of this analysis is to relate evaluation, (revealing) defects, and quality of a software under test or AUT (Application under testing).

We can use two approaches to achieve these objectives :--

A) Static analysis methods where the software artifact is examined manually,
or with a set of tools, but not executed.

B) Dynamic analysis methods where the software artifact is executed
using a set of input values, and its output behavior is then examined
and compared to what is expected.

Saw Practices :--

These are the Management Check in SDLC Phases.

NFR Testing

NFR Testing:--

Non-Function Requirement Testing is a type of testing in which test user test only "Requirements".

It is not linked to core functions, it just test the requirements.

Non-Functional Requirement (NFR) testing, also known as Non-Functional Testing, focuses on evaluating the attributes of a software system that are not directly related to its functional behavior. NFRs define the qualities and characteristics of a system, such as performance, usability, security, reliability, scalability, maintainability, and compatibility.

NFR testing aims to ensure that the software system meets these non-functional requirements and performs optimally in real-world scenarios. Here are some common types of NFR testing:

Performance Testing: This type of testing evaluates how well the system performs under various workloads and measures its response time, throughput, scalability, and resource usage.

Usability Testing: Usability testing focuses on assessing the user-friendliness of the system, including ease of navigation, intuitiveness, and user satisfaction.

Security Testing: Security testing involves identifying vulnerabilities and weaknesses in the system's security measures, such as authentication, authorization, data protection, and protection against potential threats.

Reliability Testing: Reliability testing aims to ensure that the system operates consistently and reliably over a specified period and under varying conditions, including stress testing, load testing, and stability testing.

Scalability Testing: This type of testing assesses the system's ability to handle increased workload, user concurrency, or data volume and maintain its performance.

Maintainability Testing: Maintainability testing examines how easy it is to maintain and support the system, including aspects such as code readability, modularity, and the ability to make changes or fixes efficiently.

Compatibility Testing: Compatibility testing verifies that the software system functions correctly across different platforms, browsers, operating systems, and hardware configurations.

NFR testing helps ensure that the software system not only meets functional requirements but also delivers the desired performance, usability, security, and other non-functional aspects. By thoroughly testing these non-functional requirements, organizations can enhance the overall quality and user experience of their software systems.

Test Plan Contents

Test Plan contents:--

1) Test Objectives.
2) Test Strategy.
3) Test Environments.
4) Test Specifications.
5) Test Schedule.
6) Test Plan Review.

Static Testing and its Examples

Static Testing:-- Static Testing is a type of testing in which tester checks the code only, he did not run the code to see its output.

Examples:-- Syntax Checking ; Structure Investigation ; Inspection.

The Software Development Cycle !

The Software Development Cycle!

1. Programmer produces code he believes is bug-free.

2. Product is tested. 20 bugs are found.

3. Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren’t really bugs.

4. Testing department finds that five of the fixes didn’t work and discovers 15 new bugs.

5. Repeat three times steps 3 and 4.

6. Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.

7. Users find 137 new bugs.

8. Original programmer, having cashed his royalty check, is nowhere to be found.

9. Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.

10. Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.

11. Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.

12. New CEO is brought in by board of directors. He hires a programmer to redo program from scratch.

13. Programmer produces code he believes is bug-free.

And the cycle continues... .