Writing Test Cases is Verification or Validation?
Executing Test Cases is Verification or Validation?
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 |
1 Crystal Ball 1.1 Purpose This is a simple tool, for entertainment purposes only. 1.2 Scope Only for registered user. 1.3 User Interface Single page with graphic of crystal ball, and text box for typing question. User has to type her question in text box outside ball. Reports: - On ‘submit’, the system needs to access any one of the pre-stored responses at random and display in a graphical, visually appealing manner in the crystal ball. - Audio / graphical changes need to be built in, for added user experience enhancement, like music, sound effects, visual changes. Need to get details.
write test case for pen cap if it is not present?
build 1 bug is raised and it was closed by developer and build 2 is released in build 2 also same bug raised what is the satus of that bug. 1>reopen 2>open 3>new 4>defered
1.1 Purpose This tool is also a simple tool, but will be graphics- intensive, and will access the 3 databases (card databases) used in Tarot. 1.2 Scope Only for registered user. 1.3 User Interface - No questions asked, parrot pulls out tarot card - Inside Parrot application, User just have to click on a link saying ""XXXX"" to activate the tool. - Shown is the card of the day, from pack of Tarot cards(78 in number) with fixed graphics, animation, audio. Output: - Graphic-rich display of randomly selected card with detailed meaning, with links to tarot tool. - Graphics: Flying / walking parrot, emerging and choosing a card, displaying the same, and continuing to interact based on card meaning. - The cards also need to carry a brief 1/0 meaning, which will trigger a 1/0 behavior from the parrot (sympathy/making fun/crying or congratulating/smiling/winking)
Explain the branch coverage testing?
testcases for waterbottle
test case for pen?? with actual value and expected calue
i want to write the test cases for sorting the records in a table according to date wise.this is the functionality ,that is the latest record should come on the top can any one tell me the test cases for this thanks in advance:)
write test cases on file open dialog box in notepad
1. Buzz Words 1.1 Purpose Allow user easy access of content based on key/popular words 1.2 Scope All the tags at the portal. 1.3 User Interface - Tags are usually hyperlinks that lead to a collection of items that are associated with the tag. - Click takes you to page similar to Search Result page, should search all content and not only articles - Based on Most Viewed only 1.4 Interfacing/Sourcing Details - Need to develop an application which works on algorithm to calculate size/color of Buzz words. - In phase 1 algorithm will be pretty straight forward of calculating dimesion of Buzz words by going by ""Most Viewed/Visited"" words. Need to get exact algorithm.
what is parametrization ? How do you parametrize in qtp ?
pliz anyone give suggest me the test cases for shorting numbers in asc/desc order.