STLC & QC Testing

List down all the Models of SDLC

1. Waterfall Model
2. Iterative Model
3. Spiral Model
4. V-Model (Vee Model)
5. Agile Model
6. RAD Model (Rapid Application Development)
7. Prototype Model
8. Incremental Model
9. DevOps Model
10. Scrum Model

What is STLC? Also, explain all stages of STLC

STLC stands for Software Testing Life Cycle. It is a set of activities carried out to perform software testing effectively. The primary goal of STLC is to ensure that the software being developed meets the quality standards, is free from defects, and satisfies the requirements specified by the stakeholder

1. Understanding: Testers read and understand what the software should do.
2. Planning: They make a detailed plan of how to test the software, including what needs to be tested, when, and how.
3. Making Test Cases: They create step-by-step instructions for testing different parts of the software.
4. Setting up Testing Environment: They prepare the computers and software needed for testing.
5. Testing: They actually test the software, following the instructions they created earlier.
6. Finding and Fixing Problems: If they find any issues or "bugs" during testing, they report them so they can be fixed.
7. Reporting: Testers make reports about what they found during testing and share them with the team.
8. Finishing Up: Finally, when all the testing is done and everything looks good, they close the testing process and get ready to release the software.

As a test lead for a web-based application, your manager has asked you to identify and explain the different risk factors that should be included in the test plan. Can you provide a list of the potential risks and their explanations that you would include in the test plan?

1. **Security Risks: **Potential vulnerabilities leading to unauthorized access or data breaches.
2. Performance Risks: Concerns about slow response times or scalability issues under heavy loads.
3. Compatibility Risks: The application may not function correctly across different browsers or devices.
4. Integration Risks: Issues with third-party systems or APIs causing functionality problems.
5. Usability Risks: Poor user experience due to confusing interfaces or accessibility issues.
6. Data Integrity Risks: Risks related to inaccurate or inconsistent data handling.
7. Dependency Risks: Problems with third-party services impacting application functionality.
8. Regulatory Compliance Risks: Failure to meet industry standards or legal requirements.
9. _Maintainability Risks: _Challenges in maintaining or enhancing the application due to code quality issues.
10. User Traffic Risks: Risks of performance degradation or downtime during peak usage periods.
11. Data Loss Risks: Potential data loss or corruption due to system failures or bugs.
12. Scalability Risks: Concerns about the application's ability to handle increasing loads or future growth.

Your TL (Team Lead)has asked you to explain the difference between quality assurance (QA) and quality control (QC) responsibilities. While QC activities aim to identify defects in actual products, your TLis interested in processes that can prevent defects.

How would you explain the distinction between QA and QC responsibilities to your boss?

Quality Assurance (QA) focuses on preventing defects by implementing processes and procedures throughout the development lifecycle to ensure quality standards are met, while Quality Control (QC) involves identifying and correcting defects through inspection and testing of the actual products or deliverables. QA is proactive, aiming to establish robust processes, while QC is reactive, dealing with defects after they have occurred. Both QA and QC are essential for ensuring product quality, operating at different stages of the development process to achieve quality objectives effectively.

*Difference between Manual and Automation Testing? *

Manual testing and automation testing are two different approaches to software testing, each with its own advantages and use cases.