Interested to Buy Any Domain ? << Click Here >> for more details...
Defect Migration
"Defect Migration" means that error is early project
documents lead to errors in later documents. For example,
an incorrect requirement leads to an incorrect set of
speacifications, which leads to design errors, which leads
to coding errors, which lead to failures when we test
against user expectations.
a. How will you prevent Defect Migration?
b. Why do you think preventing Defect Migration is
important?
- 1 Answers
- 4302 Views
- ISB, I also Faced
- E-Mail Answers
Answer / kaminee
a. Preventing Defect Migration can be taken care of only by
keeping a close look on the requirements doc's itself and
making things(requirements) clear and specified before hand
so that they don't lead to misunderstandings or ignorance
of any requirement. All the requirements and all the points
that seems to be doubtful should be reconfirmed may it
irritates the customer at first place or may the product be
delivered late, as at the end they(customer's) would be
statisfied with the END PRODUCT which will not carry such
migration defects.
b. Defect Migration is IMPORTANT coz the late it is
detected in the Development Cycle, the more it will cost
the company in terms of Money. Moreover it will affect the
reputation of the company as for us(company) customer's
disappointment is not expected at all.
| Is This Answer Correct ? | 1 Yes | 0 No |
i am in a small size software house join as a Jnr. software Testing Engineer so here is project is on Coding and almost finished stage, no Test cases or any QA activities done b4 now can any body explain me how can i continue... m realy depresd coz m just doing manual testing by running the process n m good in this phase but i wanna know abt is QA is just doing that way....plz help me
Hi there Does anybody can respond to my Questions? Is some one there to answer my Questions posted in Software testing category.pls E-mail to sunitht27@yahoo.com
Where do you get your expected results?
Explain Test Plan with example? Explain following in the test plan with examples What is being tested? What are pass/fail criteria? When will each test occur? What Hardware & Software environment is required? What features must be tested? What features will not be tested? What are the responsibilities of individuals & organisation in the project?
what is the difference between the focused and enabled?
what is traceability matrix?
1.What is the different b/w error,defect,Bug?
If any customer will raise the change request, it falls under developer part or QA part?
Inspections, walkthroughs and Reviews comes under QA or QC?
what is cause effect graph & exp its types?
Please give me example of - 1. High Severity and High priority Bug ? 2. High Severity and low priority Bug ? 3. High priority and low severity Bug ? 4. Low Severity and low priority Bug ? Thanks
What is difference between web based testing and windows based testing ?
Automation Testing 
