What is the difference between test case result and a bug?
Answers were Sorted based on User's Feedback
Answer / murthy
Test Case Result is nothing but whether the test case is
PASS or FAIL.
If it is FAIL then the tester should need to raise a bug
for that. We will report it as a bug when we dont get the
result as expected.
| Is This Answer Correct ? | 10 Yes | 1 No |
Answer / salman
Test Case Result is nothing but whether the test case is
PASS or FAIL.
If it is FAIL then the tester should need to raise a bug
for that. We will report it as a bug when we dont get the
result as expected////ha ha ha ha sorry i am copy to first
qustion
| Is This Answer Correct ? | 5 Yes | 1 No |
Answer / anil nakhate
testCase result: - To check the expected result match to
actual result means to check test case paas or fail,
if test case expected result does not match to actual result
then we log the bug,
| Is This Answer Correct ? | 4 Yes | 1 No |
Test case are creat by tester on the basis of available
requirements for particular system/ component . test case
is set cases of which define the set of steps on different
condition, environment what we fallows to test the each
componet or technology of the system .
when we have writen test cases , then we execute them to
validate those test case ,but when we get unexpected result
on execution then we find bug and to fix that bug we have
to sent all the details of that bug to developer so that
developer can easily understand and fix. this document is
called bug report.
| Is This Answer Correct ? | 2 Yes | 0 No |
Test case result is called as deviation. Deviation from
expected result to actual result.
When we come across such things ( deviation) we write it
in bug report and call it as bug and then they raise a bug
and inform to developers about the bug or deviation.
| Is This Answer Correct ? | 2 Yes | 1 No |
Which types of testing do u do in u r organisation.
What do you think the role of test-group manager should be
what is Difference between entry criteria and exit criteria ?
what is deadlock in manual testing?what is another name for this deadlock?
What is the diffrence between BUILD & RELEASE ?
Does we make documentation for all defects?
How does the Priority matters. Will it affect only the Business impact or Functional impact as well?
I m writting the test cases in Excel sheet. After wrting test cases for version 2.0.0 If there is new feature added in build 2.0.1, I will write test cases for newly added feature. Then 3.0 version release for testing with new feature. I will write test cases for newly added feature 3.0 But if in between 2.0.2 build release for testing with same feature of 3.0.Then should I have to write test cases for same feature again? If not --> when 2.0.2build again release for testing after 2months then How should I came to know that I have to run these test cases on 2.0.2build?
What is bug life cycle?
How can I done a Web Testing? Which steps are include in it?
what r the best jobsites for manual and automation testing? except testingken.com
How do we perform critical section first (Integration testing) at specification requirement stage of SDLC? I suppose this is incorrect question as integration testing can be initiated when: * The relavant individual code modules have been designed.please correct me if i am wrong