if u have 10 inputs & you written 500 testcases for
that.out of this u found 20 defects.as a tester how u found
from which requirement that a particular defect will occur.

Answers were Sorted based on User's Feedback



if u have 10 inputs & you written 500 testcases for that.out of this u found 20 defects.as a t..

Answer / rajasundar

Good Question.

Ofcourse through Tracebility Matrix.
In detail..
If you are writing 500 testcases for 10 inputs then all the
test cases can not be direct cases; means, dependent test
cases should be there(test case depends on another
testcase).

So if a test case is failing then obviously the dependent
test cases will also fail. But usually we use to say that
the dependent cases are blocked(instead of fail) because of
the failed test case.

Take an edit box in the screen.
The requirement could be:
User is allowed to enter the values in the username and it
should accept 10 chars only.
Now, consider the following test cases for this requirement.

1. User able to enter data in username field.
2. Check for max. length of username field.

Assume the first case fails.i.e, the edit field doesn't
allow the user to enter the values;what happens to the
second case ? The tester cannot execute the second case as
he cannot enter the data into edit field.In this scenario
the second case is said to be blocked by case 1 and both
belong to the same requirement.

Usually in the tracebility matrix, we use to map the test
cases developed for the particular requirement.Say, if you
are developing 10 cases for a requirement and 1 case is
failing and remaining 9 cases are passed, then the
tracebility matrix does not say the requirement is passed.
Only if all the 10 cases of the requirement are passed then
only the tracebility matrix shows the requirement is Passed.

Is This Answer Correct ?    5 Yes 0 No

if u have 10 inputs & you written 500 testcases for that.out of this u found 20 defects.as a t..

Answer / rama

Through Traceability Matrix

Is This Answer Correct ?    3 Yes 0 No

if u have 10 inputs & you written 500 testcases for that.out of this u found 20 defects.as a t..

Answer / shravan kumar akula

We can check it out by traceability Matrix-

Traceability Matrix is nothing but No of test cases executed
to that of the requirements.


Shravan Kumar Akula

CTT me - Coolshravan4u@yahoo.co.in, If u have any queries.

Is This Answer Correct ?    0 Yes 0 No

if u have 10 inputs & you written 500 testcases for that.out of this u found 20 defects.as a t..

Answer / koteswara rao.k

Obviouly through Traceability matrix.

Def : mapping between the Requirements with our Test cases .
so from this point of level we can understand easily the
requirements .

Pre-requisite : You should thorouly known the srs or else
wireframes Docs of the basic application

koteswara.9.rao@gmail.com any concerns or help .

Is This Answer Correct ?    0 Yes 0 No

if u have 10 inputs & you written 500 testcases for that.out of this u found 20 defects.as a t..

Answer / abhishek

Level of Testing

Functional Testing: Functional testing involves testing the application against the business requirements. The goal of functional testing is to verify that the application is behaving the way it was designed to.

Unit Testing: Individually and independently testing of smallest testable parts of an application.

Integration Testing: When individual software modules are combined together and tested as a group than it is known as Integration Testing.

Smoke Testing: Preliminary testing to reveal simple failures severe enough to (for example) reject a prospective software release or build.

Sanity Testing: Very brief run-through of the functionalities to assure that part of the system or methodology works roughly as expected.

System Testing: Testing conducted on a complete, integrated system to evaluate the system’s compliance with its specified requirements.

Regression Testing: Retesting of a software system to confirm that changes made to few parts of the codes has not any side affects on existing system functionalities.

Acceptance Testing: Formal testing with respect to user needs, requirements, and business processes conducted to determine whether a system satisfies the acceptance criteria.

Alpha & Beta Testing: Alpha Testing is conducted by a team of highly skilled testers at development site whereas Beta Testing is always conducted in Real Time environment by customers or end users at their own site.

End to End Testing: End to End Testing is usually executed after functional and system testing. It uses actual production like data and test environment to simulate real-time settings. End-to-End testing is also called Chain Testing.

Is This Answer Correct ?    0 Yes 0 No

Post New Answer

More Manual Testing Interview Questions

What do you mean by peer rieviews

6 Answers   Aspire,


What is the concept of introducing a small change to the program and having the effects of that change show up in some test?

3 Answers  


What is the difference between Build Management and Release Management ?

1 Answers   CTS,


send the senario template

0 Answers  


What is CMM and CMMI?

4 Answers  






9. What drives your interest in Web accessibility?

0 Answers  


How to conduct Regression Testing Manually?

9 Answers   FIC,


What is Conventional & Unconventional testing?

1 Answers  


what is Latent Bug?

9 Answers   MBT,


what is fault?

3 Answers   Wipro,


What is severity ?

4 Answers   CSS,


hai friends i need a general test cases for check box,drop down button and radio butoon can anybody reply me plz..........thanks in advance

0 Answers  


Categories