software testing life cycle?
- 11 Answers
- 14143 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / gyaneendra patro
The above answer can be defined as Bug life cycle. Software
testing life cycle is something else.
| Is This Answer Correct ? | 3 Yes | 0 No |
Answer / happy
The different phases of testing life cycle are
1)Test plan preperation(from srs,project schedule,usecases
etc)
2)Test case preperation
3)Execution of testcases
4)Bug reporting
5)regression testing
6)Test summary prepration and analysis
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / raghavendra chitral
STLC is a systematic approach to carry out the testing in
phased manner wherein we have the following phases.
1. System Study
2. Prepare Test Plan.
3. Prepare Test Cases.
4. Prepare Traceability Matrix.
5. Test Case Execution.
6. Defect Tracking.
7. Prepare Test Execution Report.
With the above STLC completes from customers view point.
But for testing point of view we have one more phase
8. Retrospection meeting wherein all the merits and
demerits or +ve and -ve processes followed during testing
process are discussed and a paper is prepared which aids in
next project.
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / guest
Ragavendra, You are right! But I need a brief description
on this
| Is This Answer Correct ? | 1 Yes | 0 No |
Answer / rams
STLC consists of six (generic) phases:
• Test Planning,
• Test Analysis,
• Test Design,
• Construction and verification,
• Testing Cycles,
• Final Testing and Implementation and
• Post Implementation.
•Test Planning
This is the phase where Project Manager has to decide what
things need to be tested, do I have the appropriate budget
etc. Naturally proper planning at this stage would greatly
reduce the risk of low quality software. This planning will
be an ongoing process with no end point.
Activities at this stage would include preparation of high
level test plan-(according to IEEE test plan template The
Software Test Plan (STP) is designed to prescribe the
scope, approach, resources, and schedule of all testing
activities. The plan must identify the items to be tested,
the features to be tested, the types of testing to be
performed, the personnel responsible for testing, the
resources and schedule required to complete testing, and
the risks associated with the plan.). Almost all of the
activities done during this stage are included in this
software test plan and revolve around a test plan.
•Test Analysis
Once test plan is made and decided upon, next step is to
delve little more into the project and decide what types of
testing should be carried out at different stages of SDLC,
do we need or plan to automate, if yes then when the
appropriate time to automate is, what type of specific
documentation I need for testing.
Proper and regular meetings should be held between testing
teams, project managers, development teams, Business
Analysts to check the progress of things which will give a
fair idea of the movement of the project and ensure the
completeness of the test plan created in the planning
phase, which will further help in enhancing the right
testing strategy created earlier. We will start creating
test case formats and test cases itself. In this stage we
need to develop Functional validation matrix based on
Business Requirements to ensure that all system
requirements are covered by one or more test cases,
identify which test cases to automate, begin review of
documentation, i.e. Functional Design, Business
Requirements, Product Specifications, Product Externals
etc. We also have to define areas for Stress and
Performance testing.
•Test Design
Test plans and cases which were developed in the analysis
phase are revised. Functional validation matrix is also
revised and finalized. In this stage risk assessment
criteria is developed. If you have thought of automation
then you have to select which test cases to automate and
begin writing scripts for them. Test data is prepared.
Standards for unit testing and pass / fail criteria are
defined here. Schedule for testing is revised (if
necessary) & finalized and test environment is prepared.
•Construction and verification
In this phase we have to complete all the test plans, test
cases, complete the scripting of the automated test cases,
Stress and Performance testing plans needs to be completed.
We have to support the development team in their unit
testing phase. And obviously bug reporting would be done as
when the bugs are found. Integration tests are performed
and errors (if any) are reported.
•Testing Cycles
In this phase we have to complete testing cycles until test
cases are executed without errors or a predefined condition
is reached. Run test cases --> Report Bugs --> revise test
cases (if needed) --> add new test cases (if needed) -->
bug fixing --> retesting (test cycle 2, test cycle 3….).
•Final Testing and Implementation
In this we have to execute remaining stress and performance
test cases, documentation for testing is completed /
updated, provide and complete different matrices for
testing. Acceptance, load and recovery testing will also be
conducted and the application needs to be verified under
production conditions.
Currently role is performing Specialty based testing (i.e.)
FUNCTIONALITY TESTING.
•Post Implementation
In this phase, the testing process is evaluated and lessons
learnt from that testing process are documented. Line of
attack to prevent similar problems in future projects is
identified. Create plans to improve the processes. The
recording of new errors and enhancements is an ongoing
process. Cleaning up of test environment is done and test
machines are restored to base lines in this stage.
| Is This Answer Correct ? | 1 Yes | 1 No |
Answer / prashanth
ya reallyy.. the first answer is perfectly wrong..
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / rajkumar
stlc contain some phases such as test planning ,test
development ,test execution ,result analysis ,bugtracking
and reporting .
contents of test plan
I)introduction
.objective
.reference documents
ii)coverage of testing
.features to be tested
.features not to be testd
iii)test strategy
.types of testing
.levels of testing
.test design techniques
.configuration management
.test metrics
.terminology
.automation plan
.list of automated tools
iv)base criteria
.acceptance criteria
.suspension criteria
V)test deliverables
vi)test environment
vii)resource planning
viii)scheduling
ix)staffing and recruitments
x)risks and contingencies
xi)assumptions
x)approvals
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / ranjana shanbhag
in order to get good quality and also product with no
bugs.In order to get these 2 things we need a systematic
process that is why we need software testing life cycle
| Is This Answer Correct ? | 0 Yes | 1 No |
How will you test application without any SRS or any document and also the the developer who developed the application is resigned. In short no one knows the functionality of application.
why we calling it as bug life cycle not as a defect life cycle..
What is Testers role in a s/w firm?
Expain Equivalence Class Partion with an Example?
Can you explain how one defect leads to other defects?
What is severity and priority of bug? Give some example.
How will You select the regression testcase
how do we do database testing manually.Suppose if i want to check whether a particular record is inserted in the database or not.
Why most of the software company preferred manual testing even though many automation testing tools are present in the market.
What is the Stub abd the driver ?Are these both using at the time of Top-up approach of integration testing and bottom-down approach testing .?
Define load, performance and stress testing
Write the possible positive and negative testcases for telephone.
Automation Testing 
