Tests In Software Development Change Managers Need To Know – by Alok Das
Source: Alok Das Linked In
User Acceptance Testing (UAT):
Is conducted by the end-users or clients to verify the software meets their needs and requirements.
It’s the final validation before the software goes live.
Build Verification Testing (BVT):
Also known as smoke testing.
Ensures that the build is stable and that critical functionalities work correctly before proceeding with further testing.
Unit Testing:
Involves testing individual components or modules of the software to ensure they work as expected.
Helps identify and fix bugs at an early stage.
Integration Testing:
Focuses on verifying the interactions between different components or systems to ensure they work together seamlessly.
System Testing:
Involves testing the complete and integrated software to evaluate its compliance with the specified requirements.
Covers both functional and non-functional aspects.
Regression Testing:
Ensures that new code changes do not negatively affect the existing functionalities of the software.
Involves re-running previously executed tests.
Performance Testing:
Measures the software’s responsiveness, stability, and scalability under various conditions.
Includes load testing, stress testing, and endurance testing.
Stress Testing:
Determines how the software performs under extreme conditions, such as high traffic or data load, to identify its breaking point and ensure it can handle unexpected spikes in usage.
Security Testing:
Identifies vulnerabilities and ensures that the software is protected against threats and attacks.
Exploratory Testing:
Involves testers exploring the software without predefined test cases to uncover unexpected issues or bugs.
Usability Testing:
Evaluates how user-friendly and intuitive the software is by observing real users as they interact with it.
End-to-End Testing:
Verifies the complete workflow of the software from start to finish, ensuring that all integrated components work together as intended.
Alpha Testing:
Conducted by internal teams to identify bugs before releasing the software to external users.
Beta Testing:
Involves releasing the software to a limited number of external users to gather feedback and identify issues that were not found during internal testing.
System Integration Testing (SIT):
Ensures that integrated systems work together as expected. It focuses on the interactions between different systems and components.
Functional Testing:
Verifies that the software functions as intended according to the specified requirements. It ensures that each feature works correctly.
Penetration Testing:
Simulates cyberattacks to identify security vulnerabilities.
Helps ensure that the software is protected against real-world threats.
