STLC & QA Testing

1. List down all the models of SDLC.

   • Waterfall model

     It is a universally accepted SDLC model and the whole process of software development is divided into various phases.

   • RAD model

     Rapid Application Development process is an adoption of the waterfall model.It targets developing software in a short period.

   • Spiral model

     The spiral model is a risk-driven process model.

   • V-model

     In this model the steps are planned in parallel so that the verification phases on the side and validation phases on the other side.V model joins by codiing phases.

   • Incremental model

     The incremental model is not a separate model. It is necessarily a series of waterfall cycles.

   • Agile model

     This model is used for big projects because big project is divided into smaller units/chunks/iteration that is called as sprint.

   • Iterative model

     Iterative development is a way of breaking down the software development of a large application into smaller pieces.

   • Bigbang model

     This model works best for small projects with smaller size development team which are working together. It is also useful for academic software development projects.

     1. What is STLC? Explain all stages of STLC.

The Software Testing Life Cycle (STLC) is a systematic approach to testing a software application to ensure that it meets the requirements and is free of defects. It is a process that follows a series of steps or phases, and each phase has specific objectives and deliverables. The STLC is used to ensure that the software is of high quality, reliable, and meets the needs of the end-users.

Stages of STLC

• Requirement analysis

• Test planning

• Test case development

• Test environment setup

• Test execution

• Test closure

  1. Before testing software, one of the most effective feats QA teams can perform is risk identification that brainstorms which anticipated coding or performance could probably or possibly disrupt software or system functionality. According to Software Testing Help, risk identification, which includes anything that can possibly render the deployment ineffective, ultimately prevents loss of ROI. Risks may include.

• Tight timelines

• Undefined project scope

• Insufficient resources

• Continuously changing requirements

• Natural disasters

1. Quality Assurance

• It is a process which deliberates on providing assurance that quality request will be achieved.

• QA aim is to prevent the defect.

• QA is the technique of managing quality.

• QA does not involve executing the program.

• All team members are responsible for QA.

• QA Example: Verification

Quality Control

• QC is a process which deliberates on fulfilling the quality request.

• A QC aim is to identify and improve the defecs

• QC is a method to verify quality.

• QC always involves executing the program.

• Testing team is responsible for QC.

• QC Example: Validation.

1. Difference between manual and automation testing.

Manual testing

• For observation manual testing allow human factor.

• Manual testing checks the user-friendliness.

• In manual testing investment is required for humans resources because here humans test the software instead of any software tools.

• Manual testing is time consuming because here process is done by humans or manually.

• In manual testing, there is a chance of human errors because here testing is done by humans.

• In manual testing, there is a possibility of Exploratory testing.

• In manual testing, there is no need of programming knowledge.

• Manual testing doesn’t use frameworks.

Automation testing

• For observation automation testing does not allow human factor.

• Automation testing can not give the guarantee of user-friendliness.

• In automation testing investment is required for automation tools because here testing is done by some software tools.

• Automation testing is not time consuming because here process is done by some software tools.

• In automation testing, there is no chance of human errors because here testing is done by tools.

• In automation testing, there is no permission of random testing.

• In automation testing, there is must a need of programming knowledge.

• Automation testing uses frameworks like Data Drive, Keyword etc.