Can anyone explain Boundary value Analysis and equavelance
partition with real time example
Answer Posted / rajendra
Hai Swapna ur misunderstood the Equivalence partition
technique.
This is used to create test cases,Test data.
Not for resting bugs reported and fixed in previous
build.
ok
rajendra
rajendra_penumalli@yahoo.com
Is This Answer Correct ? | 10 Yes | 6 No |
Post New Answer View All Answers
Are there more defects in the design phase or in the coding phase?
Can you please explain about the erp project
hi friends, i have completed course and project on insurance domain in mindq testing institution...can any working employee please tell me ,which notes( testing subject notes,project notes)i have to prefer first.i was studied both notes and getting confussion.one of my friend got job throughly only project notes and said that project notes is enough to get job.in which way ,i have to prepare interview( which important topics first ), if you are follow any strategy to interview purpose,pls send me important topics list.
Can you explain usability testing?
A form has four mandatory fields to be entered before you submit. How many numbers of test cases are required to verify this? And what are they?
write test case for gmail sign up page?
what types of bugs will we find out in banking projects
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 ?
What are the RBI rules has to follow by a bank for online precesseing. ?
how to explain banking domain project in testing?
what r u r responsibilities in current project
value momentum
Why testers wil prepare useracceptance testcases,system testcases and integration testcases,What is the differenece between all this test cases
What is the first test in software testing process?
list of methods that is used to document the requirements of a software.