What are the manual testing concepts?

Manual testing involves the process of manually checking software for defects. Here are some fundamental manual testing concepts that you should be familiar with:

1. Test Case:

   • A set of conditions or variables under which a tester will determine whether an application or system behaves as intended. Test cases are designed to validate specific features or functions.

2. Test Plan:

   • A comprehensive document that outlines the scope, approach, resources, schedule, and deliverables of the testing activities. It serves as a guide for the entire testing process.

3. Test Suite:

   • A collection of test cases grouped together based on a common objective or functionality. Test suites are organized to efficiently execute and manage testing efforts.

4. Test Execution:

   • The process of running test cases against the software to identify defects. It involves following the steps outlined in the test cases and documenting the actual results.

5. Defect or Bug:

   • A flaw in the software that causes it to behave unexpectedly or not as intended. Defects are identified during testing and reported to the development team for resolution.

6. Regression Testing:

   • Testing conducted to ensure that changes or additions to the software (new features, bug fixes) do not negatively impact existing functionalities. It helps maintain the overall integrity of the application.

7. Test Environment:

   • The setup of software and hardware required to execute test cases. It includes the operating system, databases, browsers, and other components necessary for testing.

8. Smoke Testing:

   • A preliminary test that checks whether the basic functionalities of the application work as expected. It is often performed before more in-depth testing to quickly identify critical issues.

9. Sanity Testing:

   • A subset of regression testing that focuses on specific areas of the application to ensure that recent changes have not adversely affected those functionalities.

10. Black Box Testing:

    • Testing where the tester is unaware of the internal code structure. It focuses on validating inputs and outputs without knowledge of the application's internal workings.

11. White Box Testing:

    • Testing that involves an understanding of the internal code and logic of the application. Testers design test cases based on the internal structure of the software.

12. Grey Box Testing:

    • A combination of both black box and white box testing. Testers have partial knowledge of the internal code structure and use a mix of functional and structural testing techniques.

13. Positive Testing:

    • Verifying that the software behaves as expected under normal or expected conditions.

14. Negative Testing:

    • Testing conducted to ensure that the software handles unexpected or incorrect inputs gracefully, producing appropriate error messages or responses.

15. User Acceptance Testing (UAT):

    • The final phase of testing where end users validate the software to ensure it meets their requirements and is ready for production use.

16. Alpha Testing:

    • Testing conducted by the internal development team before releasing the software to a select group of external users.

17. Beta Testing:

    • Testing conducted by a group of external users before the software is released to the general public. It helps identify issues that may not have been found during earlier testing phases.

Understanding these manual testing concepts is crucial for effectively planning, executing, and managing the testing process. Keep in mind that these concepts may vary in their implementation based on the specific methodologies and practices adopted by different organizations.