Writing Test Cases is Verification or Validation?
Executing Test Cases is Verification or Validation?
- 9 Answers
- 15537 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / ganesh
Writing test cases is neither verification or validation as
nothing is performed on application.However reviewing test
cases is verification. This is to confirm that the test
cases are built based on requirments.
Executing test cases is validation.
Let me know if I am not correct.
| Is This Answer Correct ? | 36 Yes | 4 No |
writing test case is a test data required to test the
application.Test data may be input/setup/procure to test.so
it should not be verification or validation.
executing test cases is a vaildation.since checking the
correctness of created application /code with the test data.
| Is This Answer Correct ? | 18 Yes | 7 No |
Answer / kailash
Writing Test cases is not verification also not validation.
verification is checking that whether right process is
followed. its done through review, inspection and
walkthrough. On the other hand when we execute the test
case then we check whether right product is build. This is
called validation
| Is This Answer Correct ? | 7 Yes | 1 No |
Answer / padmakar kulkarni
Just writing the Test Cases is more of a preventive
mechanism. Executing the test cases is where you actually
validate the written test cases.
| Is This Answer Correct ? | 3 Yes | 1 No |
Answer / vic
Writing test cases is neither verification nor validation.
It is design, even if in during the process the test
designer can have to verify requirements.
Executing test cases is definitely validation
| Is This Answer Correct ? | 1 Yes | 1 No |
Answer / vijendra.jois
As Verification mean conformance of the system to the
specification and Validation mean functionality defined in
the requirement is intended behavior ofthe product it is
done actual testing (dynamic analysis) so executing test
case is validation
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / mjt
It depends on what you are trying to accomplish with the
tests. Writing the test cases can be the administrative
side of both verification and validation. During
verification you are attempting to see if you built the
software or hardware correctly. During Validation you
intent is to ensure that you built the correct software or
hardware (according to requirements). If you do not have
separate objectives you are doubling your work in one area.
Now, as for executing test cases you again are performing
the second section for each test phase. If you are not
writing and executing test cases for each phase, have you
really performed the testing necessary to gather the
required evidence?
In short, writing and executing test cases are both a
function of verification and validation. If you do not have
test cases for each test phase both written and executed
you cannot prove that the test phase was completed and
closed out. One difference between the two is that from an
audit perspective, your validation test cases must maintain
traceability to requirements and be reviewed, approved, and
controlled before execution can begin.
| Is This Answer Correct ? | 1 Yes | 2 No |
Answer / irfan
writing test cases is averification and execute test
casesis avalidation
| Is This Answer Correct ? | 5 Yes | 10 No |
testcases for waterbottle
what is login and login in testcases we write in testcaseid
There is French dictionary and if you want to check it in English and there is no documentation available then how you will test it and write a test case and Test scenario on it.
How to write test case for this scenario. The system shall allow for a wild card search for the last name with a minimum of one character
You have designed test cases to provide 100% statement and 100% decision coverage for the following fragment of code. If width > length then biggest_dimension = width else biggest_dimension = length end_if the following has been added to the bottom of the code fragment above. Print 'biggest dimension is ' &biggest_dimensionprint 'width: ' & width print 'length: ' & length how many more test cases are required?
explain end to end scenario's for online Money transfer in Banking Domain?
what is parametrization ? How do you parametrize in qtp ?
Roads concatenation Problem Consider we have some GIS (Geo Information System) operating over some road network. Each road represented as array of two-dimensional geographical points. Road network is a set of roads. System has function called Concatenate(). This function takes raw road network and should return optimized road network. Optimization lies in concatenating roads with matching start or end points, i.e. if road AB end point matches road BC start point, then optimized network should contain concatenated road AC. Optimized network shouldn’t contain two roads which can be concatenated. Your task is to suggest set of test cases for Concatenate() function in order to make sure it works correctly. public interface IPoint { double Lat { get; } double Lon { get; } } public Road : List<IPoint> { } public RoadNetwork : List<Road> { } public RoadNetwork Concatenate(RoadNetwork roads);
explain with examples- transaction testing, syntax testing, domain testing, logic testing, and state testing.
write test cases for test cases...?
If there are 10 steps for a test case. and for this test case there are 6 expected results. should I write 6 exp. results in the Expected Result column for a single tes case
Sample test cases for data conversion(Utility billing system)
Automation Testing 
