Impact of slow load time on website performance

An estimated 4.4 billion in revenue loss is recorded annually due to poor web performance.

Impact on Revenue / Sales:

• If an e-commerce site makes $100,000 per day, a 1-second page delay could cost you $2.5 million in lost sales every year.
• 1 second of load lag time would cost Amazon $1.6 billion in sales per year.

Main Issues:

Consequences of slow page load:

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

Software Testing Real Time Examples

 Classification of Software Testing:

Techniques of Black Box Testing:

1. Equivalence Partitioning

2. Boundary Value

3. Decision Table

4. State Transition

5. Error Guessing

Equivalence Partitioning VS Boundary Value Analysis

Types of Testing Methods:

Black Box VS White Box

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

Performance Testing Real Time Examples

 Performance Testing:

Types of Performance Testing:

1. Load Test

2. Stress Test

3. Scalability Test

4. Soak Test

5. Load vs Stress

JMeter Works:

Thread Group

Thread count vs Loop count

Duration Assertion

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

Introduction to Postman API Testing

 Postman API:

• Postman is an API Development Environment that helps developers easily test and work with APIs.
• It is used for backend testing where we enter the end-point URL, send the request to the server, and receive the response back from the server.
• It provides an easy-to-use interface for developing, testing and debugging REST APIs.
• Postman also includes a comprehensive library of pre-defined requests and response objects, making it an ideal tool for quickly testing and prototyping APIs.

Request Methods:

• GET - Get requests are used to retrieve information from the given URL.
• POST - To send the new data to an API.
• PUT - This method is used to update the existing data.
• DELETE - This is used to remove or delete the existing data.

API test actions:

1. Verify the correct HTTP status code.
2. Verify response payload: Check valid JSON body and correct field names, types, and values - including in error responses.
3. Verify response headers: HTTP server headers have implications on both security and performance.
4. Verify correct application state: This is optional and applies mainly to manual testing, or when a UI or another interface can be easily inspected.
5. Verify basic performance sanity: If an operation was completed successfully but took an unreasonable amount of time, the test fails.

HTTP Status Codes:

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

The Essential Performance Testing Metrics Every Developer Should Know

1.  Processor Usage: Time spent by the processor to execute non-idle threads.
2. Memory use: The available physical memory to process on a system.
3. Disk time: It is the time taken by the disk to read or write a request.
4. Bandwidth: Bits per second used by a network interface.
5. Private bytes: A specific number of bytes allocated to a particular process.
6. Response time: The time between the user’s request and the first response character.
7. Throughput: Rate of requests received per second by a network. (The formula is Throughput = (number of requests) / (total time). )
8. Maximum active sessions: Maximum number of sessions that may stay active at once.
9. Thread (user) counts: Determining the well-being of the application by checking the number of running and active threads.
10. Latency - JMeter measures the latency from just before sending the request to just after the first response has been received.
11. Think Time - the time between two transactions of user actions. 
    (Login -> Think Time -> Search -> Think Time -> Logout). 
    The average thinking time could be in the range of 3 to 10 seconds for a normal user.
12. Error rate - Measures the number of errors that occur in each request.
13. Network latency - Measures the time it takes for a request to travel from the client to the server.
14. Transaction time: Measures the time it takes for a transaction to complete.
15. Resource utilization: Measures the number of resources used by the server to handle requests.
16. Memory usage: Measures the amount of memory used by the server to process requests.
17. Load test scalability: Measures how well the server can handle an increasing amount of requests.
18. Page load time: Measures the time it takes for a web page to load.

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.