Explain Boundary value analysis, Equivalence partitoning
and Error guessing?
Answer Posted / aa
Boundary value analysis : Designing test cases at boundary
values. If field take values from 10 to 20 numbers,
following are the boundary values which is taken care while
doing testing.
Valid boundary values 10, 11, 19, 20
Invalid Boundary values 9, 21.
Equivalence partitioning : Designing test cases by deviding
the input values in to equivalence partitions.
valid Equivalence partitions 14 or 18
Invalid equivalence partitions 5, 26
Error guessing : From testers experience , are able to guess
where bug will come and in which scenario.
| Is This Answer Correct ? | 5 Yes | 1 No |
Post New Answer View All Answers
What are the different ways to check a date field in a website?
What are the factors affecting a manual testing project and what are the ways to overcome it?
Can you explain function points?
Hi friends I am kranti completed my IT diploma in 2005 & after that complete my software testing course. Now I am working in small software form as software tester. I have 2 + year experience in manual testing. Now I wan to change company. Plz told me is there any effect that I can not have any degree although I have 2 + experience ?
How many types of api testing are there?
6 what do you like least about testing?
Hi, I want "Intergraph" placement papers for experienced people which was conducted recently in Hyderabad. Thanks, Purnima.
Write notes on apparel testing equipments.
through which phases a software ttester need to pass like as a junnior test engineer,team lead,project lead,etc.? which is the final stage of your promotion and how will u achieve?
After insert the record in front-end, how will you check the back end by manually? Please explain?
Hi friends, currently i am working with banking domain project in the part of testing..what kind of questions will be ask at interviews.. can anybody listout the project oriented questions which are asked in interviews...
Difference between Stakeholder and Relevant Stakeholder?
What are the properties of a good requirement?
How does your preferred work style work with the ideal test-manager role that you just described? What is different between the way you work and the role you described?
What are the tasks of test closure activities in software testing?