https://www.javatpoint.

com/software-testing-life-cycle

Q) What is Quality Control and Quality Assurance?

Quality Assurance:
 Defines standards and methodologies to follow to meet customer requirements.
 QA is the process of creating deliverables.
 QA is responsible for the entire software development life cycle

Quality Control:
 Ensures that standards are followed while working on the product.
 QC is the process of verifying the deliverables.

Q) What is SDLC?
 Software development life cycle (SDLC) is a structured process that is used to
design, develop, and test good-quality software.

Q) What are the different stages of SDLC?

SDLC involves 6 stages or phases

 Stage 1: Planning and Requirement Analysis:

 The senior members of the team gets the inputs from all the stakeholders
and domain experts.
 Planning for the quality assurance requirements and identifications of the
risks associated with the projects is also done at this stage
 Business analyst and Project organizer set up a meeting with the client to
gather all the data like what the customer wants to build, who will be the end
user, what is the objective of the product.

 Stage2: Defining Requirements

  Once the requirement analysis is done, the next stage is to certainly
represent and document the software requirements and get them accepted
from the project stakeholders.
 This is accomplished through "SRS"- Software Requirement Specification
document which contains all the product requirements to be constructed and
developed during the project life cycle.
 Stage3: Designing the Software
 Once getting the all the knowledge of requirements, analysis, and design of
the software project.
 This phase is the product of the last two, like inputs from the customer and
requirement gathering.
 Stage4: Developing the project
 In this phase of SDLC, the actual development begins
 Stage5: Testing
 During this stage, unit testing, integration testing, system testing, acceptance
testing are done.
 Stage6: Deployment
 Once the software is certified, and no bugs or errors are stated, then it is
deployed.

Q) What is the Role of QA in the Software Development Life Cycle?

Q) What is a Software Testing Life Cycle (STLC)?

 It is a systematic approach to testing a software application to ensure that it
meets the requirements and it is free of defects

Q) What are the Phases of STLC? What are the activities performing in each phase of STLC?

 Phase1: Requirements Analysis

 The requirements of the software system are analysed.
 This phase involves understanding the software requirements and
ensuring that they are clear, concise, testable & deliverable.
 Phase2: Test Planning
 In this phase, the test objectives are defined
 Test strategy and test plan created and test effort estimated.
 Tools and resources are then determined.

 Phase3: Test Design

 In this phase tester will designing of test cases, creation of automation
test scripts and preparation of test data.
 Phase4: Test Environment Setup
  During this phase, the environment and test data are setup and a smoke
test is usually run to confirm that the environment is ready.
 Phase5: Test Execution

 This is when the actual testing takes place. Functional and non-functional
types of testing are executed, test cases and test scripts are run, bugs
logged and test results reported. Regression testing, bugs verification
and closure also belong to this phase.

 Phase6:Test Closure
 During this phase, we prepare test summary report and gather test
metrics and report them to stakeholders.

Q) What are the difference between SDLC and STLC?

Q) What types of SRS (Software Requirement Specifications) issues can be detected during
the review of requirements?
Q) How would you define that testing is sufficient and it’s time to enter the Test Closure
phase?
Q) Which phase of STLC includes bugs closure activities?
Q) How do you map STLC to SDLC? Specify what testing activities are held in each phase of
SDLC.
Q) What is the difference between static testing and dynamic testing
https://www.youtube.com/watch?v=7WNsjz3LnAk

Q) What do you understand by software testing?

Software testing is a validation process that confirms that a system works as per the

business requirements. It qualifies a system on various aspects such as usability, accuracy,

completeness, efficiency, etc. ANSI/IEEE 1059 is the global standard that defines the basic

principles of testing.

Q) What is a test plan and what does it include?

A test plan stores all possible testing activities to ensure a quality product. It
gathers data from the product description, requirement, and use case documents.
The test plan document includes the following:

 Testing objectives
 Test scope
 Testing the frame
  Environment
 Reason for testing
 Criteria for entrance and exit
 Deliverables
 Risk factors

Q) When should you stop the testing process?

The testing activity ends when the testing team completes the following milestones.
Test case execution
The successful completion of a full test cycle after the final bug fix marks the end of the
testing phase.
Testing deadline
The end date of the validation stage also declares the closure of the validation if no critical
or high-priority defects remain in the system.
Code Coverage(CC) ratio
It is the amount of code concealed via automated tests. If the team achieves the intended
level of code coverage (CC) ratio, then it can choose to end the validation.

Mean Time Between Failure (MTBF) rate

Mean time between failure (MTBF) refers to the average amount of time that a device or
product functions before failing. This unit of measurement includes only operational time
between failures and does not include repair times, assuming the item is repaired and
begins functioning again. MTBF figures are often used to project how likely it is for a single
unit to fail within a certain period of time.

Q) What do verification and validation mean in software testing?

Verification is a process that confirms that product development takes place as per the
specifications and uses standard development procedures. The process comprises the
following activities:

 Inspections
 Reviews
 Walk-throughs
 Demos
Validation is a means to confirm that the developed product doesn’t have any bugs
and works as expected. It comprises the following activities:
 Functional testing
 Non-functional testing

Q) Define black-box testing.

The tester focuses solely on the external behaviour of the software, without having access
to its internal source code.

Q) What is meant by test coverage?

Test coverage is a quality metric to represent the amount (in percentage) of testing that has
been completed. It is relevant for both functional and non-functional testing activities.

Q) Is it possible to achieve 100% testing coverage? How would you ensure it?
It’s considered impossible to perform 100% testing of any product. But, you can follow the
below steps to come closer.
 Set a hard limit on the following factors:
o Percentage of test cases passed
o Number of bugs found
 Set a red flag if:
o Test budget is depleted
o Deadlines are breached
 Set a green flag if:
o The entire functionality gets covered in test cases
o All critical and major bugs must have a ‘CLOSED’ status
Q) What are unit testing and integration testing?

 Unit testing has many names such as module testing or component testing.

 Many times, it is the developers who test individual units or modules to check if they

are working correctly.

 Whereas, integration testing validates how well two or more units

of software interact with each other.

Q) Can we do system testing at any stage?

No. System testing should start only if all modules are in place and they work correctly.

However, it should be performed before UAT (user acceptance testing).

Q) Mention the different types of software testing.

Black Box Testing

Regression testing

Smoke testing
Functional testing

Exploratory Testing

Integration Testing

System Testing

Graphical User Interface Testing

User Acceptance Testing (UAT)

Alpha and Beta testing

Unit testing

Integration testing

Shakeout testing

Performance Testing

Q) What is the purpose of the end-to-end testing?

 End-to-end testing is a testing strategy to execute tests that cover every possible

flow of an application from its start to finish.