Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / nandan kumar
Based on the requirements developers will be developed the
application and when the build#1 is released to the testing
department..test engineers will test the application and if
no defect simply stop the testing process.
If any defect is identified for the first time then they set
the status as "New" and send to developer lead.
(Here one thing we should know i.e., directly test engineers
will not send the defects to the development team..as a
tester we should send the defects to test lead first he will
analyze whether is it really a bug or not and then he sets
the severity and send to development lead).
The development lead also analyze whether is it really a
defect and if he feels it's not a defect then he will reject
the defect and set the status as "Rejected".
Hold status :
When ever the developer is confused to accept or reject the
defect then he will set the status of hold. For this they
will have separate meeting with testing dept to decide
whether it is defect or not..if it is decided as a defect
then the developers will open it otherwise the testers will
close.
Differed status:
When ever the development lead accepts the defect and wants
to rectify it after some time then he will set status as
differed.
As per the design status :
When ever the test engineer raises a defect with out having
the proper knowledge of latest requirements then the
developers will set the status as " As per the design".
Then the test engineers will go through the latest
requirements and if at all they feel it is as per design
only then they will close it otherwise re-open it.
Open status :
If the development lead accepts the defect and he will set
the status as "OPEN" and also he will set priority and
assign the defect to the corresponding developer for
rectification..when he is assigned the defects the status is
"Rectification".
Fixed status:
When ever the the defect is rectified by the developer
before releasing the next build they will set the status as
"Fixed".
And then when build#2 is released to testing team..they will
not believe blindly once they will test the application
after rectification as well if no found then they close the
testing process and set the status as "Closed" or if they
found any defect then they will send to the developers with
status as "Re-open".
This process continues continues..till the testers will feel
the product is defect free.
| Is This Answer Correct ? | 2 Yes | 1 No |
Post New Answer View All Answers
Test Cases For Router&Switch
How to write test case for view the table(i.e it is already stored in database and see the content in the table)
i) functional test cases can we consider for regression test ? or we have to write separet test cases for regression test ? ii) How to write the system test case and what are the technique shall we have to follow ?
whar are the contents in db testing test case template
Please anyone give answers for all below questions and help ? realtimers please and please share your knowledge.lot of questions left unanswered.
What is unit level testing?
What are the cases when you’ll consider to choose automated testing over manual testing?
What is the big deal about ‘requirements’?
how to connect your project in database?
Which is the best book to ref. for design the test cases/scenario in manual testing,which gives detailed idea with all the strategies ?
Changes and enhancements to system?
What r the sequences that leads to automation?
How does a coverage tool work?
can anybody tell me what is release process of company? release note?
can someone give me a brief idea about embedded testing.. i know both embedded system concepts and testing concepts.. i just want to know what we have to do for embedded testing
