4.3. Common Types of Testing

🔄 Regression Testing Purpose: Verify that new changes haven’t broken existing functionality. When: After every code change, bug fix, or release Tools: Selenium, TestNG, QTP

Regression Testing is a type of testing conducted to ensure that any new changes made to the software don't negatively impact the existing features. This is crucial because updates or bug fixes can unintentionally introduce new issues. Regression tests are performed after every code change, bug fix, or release to ensure that everything is still working as expected. Tools like Selenium, TestNG, and QTP are commonly used to automate these tests, making it easier and quicker to run them repeatedly.

Imagine you are a chef who just updated your famous pasta recipe by adding a new seasoning. After making that change, you would want to taste the entire dish again to ensure the new flavor doesn't ruin the balance of ingredients you previously developed. That’s similar to regression testing.

🔥 Smoke Testing Purpose: A quick set of tests to ensure the core system is stable enough for further testing. Example: Can users log in? Can the homepage load? Analogy: "Does the build smoke when turned on?"

Smoke Testing is performed to quickly assess whether the main functionalities of the application are working correctly before more detailed testing begins. This type of testing acts like a preliminary check to confirm that the software build is stable enough for further testing phases. It often includes basic tests such as checking if users can log in or if the homepage loads properly. The term 'smoke testing' comes from hardware tests where you would check if the device shows any signs of failure, like smoke, when you turn it on.

Think of smoke testing like pre-flight checks before a plane takes off. The pilots and crew perform simple checks to ensure the engines start and the navigation system works before the flight takes off. They want to make sure everything essential is functional before going into more complex checks.

🚿 Sanity Testing Purpose: A focused test to check if a specific function or bug fix works. Example: A defect in the cart page is fixed → test the cart flow only Note: Sanity = "Are we sane to proceed with deeper testing?"

Sanity Testing is a type of testing conducted to verify that a specific function or bug fix works as intended. Unlike broader tests, sanity tests focus on one particular area of the application after changes have been made. For example, if a defect was reported and fixed on the shopping cart page, the testing team would perform sanity tests to verify that the cart now functions correctly before moving on to further testing. It acts as a checkpoint to ensure that it is appropriate to proceed with deeper testing.

Imagine you just fixed a leaky faucet in your kitchen. Before you start using the sink for washing dishes or preparing food, you check to see if the leak is indeed resolved. If it is, then you can confidently proceed with using your kitchen normally. That’s the essence of sanity testing.

👥 UAT (User Acceptance Testing) Purpose: Ensure the system meets business needs and is ready for production. Performed By: Business users, stakeholders, sometimes Business Analysts Focus Areas: ● Real-world workflows ● Usability and behavior ● Business rule validation

User Acceptance Testing, or UAT, is the final phase of the testing process before an application goes live. Its main purpose is to ensure that the system meets the business requirements and that it is ready for actual use. This phase is performed by end users, stakeholders, or business analysts who will validate real-world workflows, usability, and adherence to business rules. This testing helps confirm that the application behaves as expected in practical scenarios.

Think of UAT like a dress rehearsal before a big play. The actors run through the entire performance to ensure everything runs smoothly and adheres to the script. If the audience (in this case, the stakeholders) finds any issues, they can address them before the opening night (the launch).

🚀 Performance Testing Purpose: Measure how the system behaves under load or stress. Subtypes: ● Load Testing: Normal expected user load ● Stress Testing: Beyond normal limits ● Spike Testing: Sudden increase in load ● Soak Testing: Sustained usage over time Tools: Apache JMeter, LoadRunner, Gatling

Performance Testing is designed to evaluate how a system performs under various conditions, especially when subjected to varying levels of load or stress. The goal is to identify potential bottlenecks in the system and ensure that it can handle expected and unexpected user traffic. Performance testing breaks down into subtypes: Load Testing checks how the system handles a normal load; Stress Testing assesses how it performs under extreme conditions; Spike Testing analyzes how it reacts to sudden increases in load; and Soak Testing examines how it performs over a prolonged period under a standard load. Tools such as Apache JMeter and LoadRunner are frequently used in these tests.

Consider performance testing like assessing the endurance of an athlete. Coaches measure how well a runner performs under different conditions—normal races, extreme weather, sudden bursts of speed, and long-distance endurance. Just as athletes need to train for various scenarios, software should be tested to ensure it functions optimally in all expected and unexpected conditions.

--