- Authentication (Auth): Verifies the user's identity.
- Authorization: Determines the user's permissions.Defines what actions the user can perform.
2. Retesting and Regression testing?
- Retesting involves testing a specific bug or issue after it has been fixed by the developer.
- Regression testing involves testing the fixed bug and the surrounding areas that may have been affected by the fix. verify that the software works as expected after changes?
Regression Testing - Testing the affected as well as the unaffected areas.
3. Black Box, White Box, Gray Box Testing:
- Black box: Focuses on external behaviour and user interactions. No knowledge of internal code or structure required. Typically performed by testers, QA engineers, or end-users. Examples: Functional testing, User Acceptance Testing (UAT), Exploratory testing.
- White Box: Focuses on internal code structure and logic. Requires knowledge of programming languages and code. Typically performed by developers. Examples: Unit testing, Integration testing, Code reviews.
- Gray Box: Combines elements of black box and white box testing. Requires some knowledge of programming and code. Typically performed by testers with programming skills or developers. Examples: API testing, Database testing, Security testing.
4. Severity: Refers to the impact or effect of a defect on the application's functionality. Measures the defect's damage or risk
Priority: How soon will the defect be fixed?
5. Test scenarios focus on what to test, while test cases focus on how to test. Test scenarios define end-to-end functions to be tested, while test cases provide instructions on how to test specific features.
6. Alpha, Beta, Gamma Testing:
Alpha: Conducted by the in-house testing team. Focus on functionality.
Beta: Conducted by external customers, end-users, or a select group. Focus on real-world usage.
Gamma: Conducted by end-users and customers. For the final validation, focus on business requirements and user expectations.
7. Equivalence Partitioning:
- Equivalence partitioning is a black-box testing technique that divides input data into partitions.
- Test cases that cover all possible input scenarios reduce the number of test cases.
Valid ages: 1-100
Invalid Ages:
Below 1 (e.g., 0, -1)
Above 100 (e.g., 101, 150)
Non-numeric input (e.g., "abc")
8. Smoke and Sanity testing
- Smoke testing - Focusing on Major functionalities in the software through positive test cases.
- Sanity testing - Focusing on Major functionalities in the software through positive and negative test cases.
10. BUG - Caused by a programming error.
ERROR - Mismatch between expected and actual output.
DEFECT - When the actual output differs from customer expectations, it is considered a defect.
MISTAKE - An error made by the user.
- Requirement Analysis
- Designing
- Coding
- Testing
- Deployment
- Maintenance
- Requirement Analysis
- Test Planing
- Test Designing
- Test Environment Setup
- Test execution
- Test Cycle Closure
- Epic - It is a complete set of requirements given by the customer.
- Sprint - It is the duration of time taken to work on 1 or more user stories. Each sprint can be either 2/3/4 weeks, depending on the customer's decision.
- Sprint planning meeting - It is a meeting which is conducted before the sprint starts.
- Sprint backlog - It is a user story which is not completed in that particular sprint and is carried into the next sprint.
- Sprint review meeting - In this meeting, the scrum master will check whether all the user stories are completely developed and tested, and it is ready to be released to the customer or not.
- It is a document which is prepared to check whether every requirement has at least one test case or not. RTM maps all the requirements with the test cases.
👋 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.