any one can explain error guessing..?it depends on
validation or functional testing? give one example ..?
- 3 Answers
- 7666 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / amit verma
Error Guessing is a one of the Testing Methodology.In which
Tester use their experience to find the bug or to write the
Test case.
I think it depends on Validation testing.
| Is This Answer Correct ? | 7 Yes | 4 No |
Answer / nagesh
error guessing:a tester with the domain knowledge&
experience,he may guess where there are chances of finding
defects, to find these defects he may prepare testcases is
called error guessing.
and it is a technique for experience based testing.it is
applicable at all levels of testing process.(verification &
validation)
| Is This Answer Correct ? | 5 Yes | 2 No |
Answer / sheetal namram
it is one of the static testing or verification methods.
and it is rearely used.
it is an ad hoc testing method as the name suggests so not
recommended.
and it comes under verification testing.
| Is This Answer Correct ? | 1 Yes | 7 No |
How to write negative testcase?
exact definition of defect tracking?
what is the similarity between black box testing and unit testing
what is defect density ? we say it is No of defects / line of code.. what is line of code ? pls if possible give some real example
Hi Friends, Please help me in providing System test cases examples Thanks in Advance
wht is test scenario?
What is test description and documentation?
Could anyone explain me how to write scenerio for login screen?
I have to write test cases for Create User, Edit User, Delete User etc. Some of the steps for Create & Edit User are same. Then Should I write refer Create User [test case Id] for common test steps to write Edit User Test case? OR I have to write separate test steps even though they are repeatable in Create user & Edit User test case.
what is metrices?
What are the Test case for the file transfer.
can any one explain the example of high servity and low priority, low servity and high priority, high servity and high priority, low servity and low priority
Automation Testing 
