What are the manual testing concepts?

Manual testing involves the process of manually checking software for defects without the use of automated testing tools. Here are some fundamental concepts in manual testing:

1. Test Case:

   • A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly. It consists of test steps, expected results, and sometimes preconditions.

2. Test Plan:

   • A test plan is a document that outlines the scope, approach, resources, schedule, and deliverables for testing. It serves as a guide for the testing process and helps in effective planning and execution.

3. Test Scenario:

   • A test scenario is a high-level description of a specific end-to-end functionality to be tested. It helps in identifying the scope of testing for a particular feature or module.

4. Test Execution:

   • Test execution involves the actual running of test cases on the software under test. It includes recording test results, identifying defects, and ensuring that the software meets specified requirements.

5. Test Suite:

   • A test suite is a collection of test cases that are grouped together for execution. It allows testers to organize and manage test cases efficiently, often based on functional or business requirements.

6. Defect/Bug:

   • A defect or bug is an unexpected behavior or flaw in the software that deviates from its intended functionality. Defects are identified during testing and need to be documented, reported, and tracked until they are fixed.

7. Regression Testing:

   • Regression testing involves re-executing a set of test cases to ensure that recent changes or enhancements in the software have not adversely affected existing functionality. It helps in maintaining software quality over time.

8. Smoke Testing:

   • Smoke testing, also known as build verification testing, is a preliminary test to check if the basic functionalities of the software work properly. It is usually performed before more in-depth testing.

9. Exploratory Testing:

   • Exploratory testing is a testing approach where the tester actively explores the application with minimal or no predefined test cases. It is often used to discover defects that may not be covered by scripted tests.

10. Boundary Testing:

    • Boundary testing involves testing the application at the limits or boundaries of its input domain. The goal is to identify defects related to input values at the edge of acceptable ranges.

11. Compatibility Testing:

    • Compatibility testing ensures that the software or application functions correctly across different browsers, operating systems, devices, or network environments.

12. User Acceptance Testing (UAT):

    • User Acceptance Testing is the final phase of testing before the software is released to end-users. It involves testing the software from the user's perspective to ensure that it meets their requirements and expectations.

13. Positive Testing:

    • Positive testing involves testing the software with valid inputs to ensure that it behaves as expected under normal conditions.

14. Negative Testing:

    • Negative testing involves testing the software with invalid inputs or unexpected conditions to ensure that it can handle errors and edge cases gracefully.

15. Traceability Matrix:

    • A traceability matrix is a document that maps and traces user requirements to test cases. It helps ensure that all requirements are covered by test cases and provides visibility into the testing process.

Understanding these concepts will provide a solid foundation for anyone starting with manual testing. As you gain experience, you can explore more advanced concepts and techniques in the field of software testing.