Answers were Sorted based on User's Feedback
Answer / revati
Equivalence portioning is a technique for testing
equivalence classes rather than undertaking exhaustive
testing for each value of the larger class.
An equivalence class is a subset of data that is
representative of a larger class.
1.If an input condition specifies a range, then there will
be one valid and two invalid equivalence classes are
defined as follows:
If the Name text field should be 5 to 10 alpha
characters. Then instead of checking 6 times Name text
field ,make one class with range <5-10> which will be
called valid class and another class will be invalid
class which will be less than and greater than the range.
2.If an input condition requires a specific value, then one
valid and two valid classes are defined.
e.g. Input data is 6 digit number, then valid class is
<6 digit> and invalid classes are (<6) &( >6)
3.If an input condition is a Boolean then one valid and one
invalid equivalence classes are defined.
e.g. True or False.
The aim is to minimize the number of test cases require to
cover these input conditions.
|Is This Answer Correct ?||4 Yes||0 No|
Answer / subhash
Equivalence Partitioning is a black box testing technique.
we use Equivalence Partitioning to divide the test case in
equivalence Partitioned Valid and Invalid.
example: Consider a credit card limit accepted only range
between(20000 to 50000).
test case will be
Less than 20000(invalid)
Between 20000 to 50000 (valid)
Greater than 50000 (Invalid)
Hope this will clear your doubt..
|Is This Answer Correct ?||3 Yes||0 No|
Answer / logu
Testing the application or field with a different set of data within a specified range.
Ex: User name should accept 2 to 6 character means we have to crate the Test case for only 2 to 6 ranges not more than that.
|Is This Answer Correct ?||4 Yes||3 No|
What are the different phases available in STLC.
What is the Stub abd the driver ?Are these both using at the time of Top-up approach of integration testing and bottom-down approach testing .?
If the product is released to client and then you found some bug which you can see in high resolution screen in testing environment but on client side it was hidden under low resolution screen and it is an important functionality in that case what would be your role as a tester?
hi frnds, i m Aman.. i was asked some ques. in an interview which r concerned with Web based Testing.. ques were like, URL Tempory in testing, other was smthin like Gateway in testing?? plz tell me answers of these questions as i dont hav knwledge abt web based testing.. thnx in advance..
What is UML and how to use it for testing?
what is fpa ?
What are two types of Metrics ?
what is 'v'model?
What is Error Seeding?
Explain Bug/Defect Life cycle?
From Quality Center, how can we take a back up of a project??