Interested to Buy Any Domain ? << Click Here >> for more details...
What is mean by Equal Partitioning
- 4 Answers
- 10439 Views
- Infosys, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
It is a technique which is used to classify the test data.
The test data can be divided into valid inputs(test data)
and invalid inputs(test data).
Example: Suppose there is a text field which accepts only
alphabets then the Equal partitions contains
Valid test data:
A-Z and a-z.
The text field should accept all the alphabets
Invalid test data:
It contains all chars other than alphabets
like
Numbers,special chars, blank( spaces)
| Is This Answer Correct ? | 22 Yes | 4 No |
Answer / anonymous
Equivalence partitioning is technique where you derieve test
cases depending on the test data. here, the test data can be
divided into different equivalence classes which can be
valid and invalid test data.
example: consider an text field which accepts input of 1 to
1000
then, the valid test data can be 1 to 1000
invalid test data can be inputs below 1
and also inputs above 1000
so we totally get three equivalence classes. i.e, within the
limits, below the limits and above the limits.
| Is This Answer Correct ? | 3 Yes | 0 No |
Answer / ramesh
A) Boundary Value Analysis(BVA):
It Is Used to Save the time in Length Testing.
Length Testing : In Length Testing we Have to Test How Many Characters You can Enter Into a Field .
Implementation Of Boundary Value Analysis:
1) Identify The Boundary(S)
2) Every Boundary Generate Three Conditions
a) Boundary Value
b) Boundary Value-1
c) Boundary Value+1
Any Value Or Condition Outside The Boundary Should Be Invalid.
Ex : In Login Page User Name Length Should Be Minimum 4 Characters And Maximum 8 Characters.
B) Equivalence Class Partitioning(ECP):
It is Used to Save the Time in Value Testing .
Value Testing : In Value Testing we Have To Test What values We Can Enter into Field .
Ex : In Login Page User Name Should Accept Only
Alphanumeric in Lower Case.
C) State Transition Testing :
Every S/W Application will have various States (User Interfaces or Screens ) . An Application State will Changes From One state to Another Based on Input Data and Operations You Carryout on the System . State Transition Testing Help Full to Check All Possible States of the Application .
Ex :
Prepare TC to Check A Customer Account Access Functionality in ATM Software Using State Transition Testing.
TC1 : Check Customer Account Access By Inserting a Valid Card and Entering Correct Pin at 1st Try.
TC2 : Check Customer Account Access By Inserting a Valid Card and Entering Wrong Pin at 1st Try and Entering Correct Pin at 2nd Try.
TC3 : Check Customer Account Access By Inserting a Valid Card and Entering Wrong Pin at 1st and 2nd Try and Entering Correct Pin at 3rd Try.
TC4 : Check Customer Account Access By Inserting a Valid Card and Entering Wrong Pin at 1st , 2nd and 3rd Try.
TC5 : Check Customer Account Access By Inserting a Invalid Card.
D) Decision Table Testing :
It is Help Full to Determine Defects Because of Mistakes Committed While specifying the Logical Operators in Code.
Decision Table Testing is Help Full to Ensure 100% Test Coverage when a Functionality is Depending on Multiple Inputs. According to Decision Table Testing Number of TC You Prepared to Ensure 100% Coverage in 2n Where n is number of Inputs.
As Per Decision Table Testing You Can Derive the Fallowing TC to Check Login
TC1 : Check Login with Valid username And Valid password.
TC2 : Check Login with Valid username And Invalid password.
TC3 : Check Login with Invalid username And Valid password.
TC4 : Check Login with Invalid username And Invalid password.
Decision Table For Login
Inputs Cond 1 Cond 2 Cond 3 Cond 4
User Name Valid Valid Invalid Invalid
Password Valid Invalid Valid Invalid
Results Display
Inbox Display
Error Display
Error Display
Error
E) Use case Based Testing:
The Tests Developed Based On The Use Cases. In A Usecase A Functionality Or Feature Would Be Described With Both Primary Flow(Positive Flow) Of Events And The Alternate Flow(Negative Flow) Of Events.
For Every Possible Positive Flow And Negative Flow, There Should Be A Test Defined.
Note: Often We Perform Use case Based Testing If The Use cases Are Available.
Use Case:
A Use Case Is A Sequence Of Steps With The Complete Set Of Primary Flow Of Events Along With The Alternate Flow Of Events Documented For A Given Requirement.
( It is a Brief Description Of Actor Actions and System Responses )
Use cases Can Be Part Of Functional Requirement Specifications, Use case Are Prepared By The Requirement Collection Team.
Benefits Of Use Cases:
1. Use case Gives A Complete Understanding On The Functionality Or A Requirement
2. They Are Considered To be The Powerful Sources For Designing The Test Cases
3. Complete Coverage In Testing Can Be Achieved Based On The Use Cases.
Use case Template:
Use case Number:
It Is An Unique Identifier Of The Use Case
Ex: Uc 1.0
Use case Name:
Ex: Payments
Actor:
The User Involved In Performing That Feature Or Functionality On The System
Action Performed:
The Operation Performed On The System By The User
Ex: Enter User Name In Login Page
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / s.kumaran
equal partition is nothing but minimum to maximum words
fr example: minimum 4 words to maximum 10 words is used in
password login.
| Is This Answer Correct ? | 1 Yes | 9 No |
Explain the smoke testing?
how to write test cases for credit card payment
What is test cases for mobile phone ?
how to write test cases for "Browse" button.
in any software company how we got the srs document.how we get it is it available in version control or in mannual we get the document
7 Answers AppLabs, Pinsoftek Infosolutions, TCS,
What are test cases for Car Locking System?
Explain the exactly meaning of test case?
What is gray box testing?
How to write test case for this scenario. The system shall compare the requested name with the Service Member Name field in the database
Give me a example that differentiate Test case Procedure,Test case Scenario,Test case Discription & test steps.
1. Buzz Words 1.1 Purpose Allow user easy access of content based on key/popular words 1.2 Scope All the tags at the portal. 1.3 User Interface - Tags are usually hyperlinks that lead to a collection of items that are associated with the tag. - Click takes you to page similar to Search Result page, should search all content and not only articles - Based on Most Viewed only 1.4 Interfacing/Sourcing Details - Need to develop an application which works on algorithm to calculate size/color of Buzz words. - In phase 1 algorithm will be pretty straight forward of calculating dimesion of Buzz words by going by ""Most Viewed/Visited"" words. Need to get exact algorithm.
How many test cases u will execute per day?
Automation Testing 
