Interested to Buy Any Domain ? << Click Here >> for more details...
What is mean by Equal Partitioning
- 4 Answers
- 10226 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 end to end scenario's for online Money transfer in Banking Domain?
Please Tell me the Real Process of a Company. My company is very small & Developer explains me the feature and I prepare the test cases according to he explained .No one is there to review what I have written in the test cases.Test cases are ok but still I have the knowlege of real testing documents i.e which documents I have to prepare What is the flow starting from requirement gathering.Please tell me ,Thanks in advance .It will really helpful to me
How to write the test cases for STP
ATM REQUIREMENT TO BE TRANSLATED INTO TEST PLAN AND TEST CASES ATM REQUIREMENT AS FOLLOWS: Requirements Statement for Example ATM System The software to be designed will control a simulated automated teller machine (ATM) having a magnetic stripe reader for reading an ATM card, a customer console (keyboard and display) for interaction with the customer, a slot for depositing envelopes, a dispenser for cash (in multiples of $20), a printer for printing customer receipts, and a key-operated switch to allow an operator to start or stop the machine. The ATM will communicate with the bank's computer over an appropriate communication link. (The software on the latter is not part of the requirements for this problem.) The ATM will service one customer at a time. A customer will be required to insert an ATM card and enter a personal identification number (PIN) - both of which will be sent to the bank for validation as part of each transaction. The customer will then be able to perform one or more transactions. The card will be retained in the machine until the customer indicates that he/she desires no further transactions, at which point it will be returned - except as noted below. The ATM must be able to provide the following services to the customer: A customer must be able to make a cash withdrawal from any suitable account linked to the card, in multiples of $20.00. Approval must be obtained from the bank before cash is dispensed. A customer must be able to make a deposit to any account linked to the card, consisting of cash and/or checks in an envelope. The customer will enter the amount of the deposit into the ATM, subject to manual verification when the envelope is removed from the machine by an operator. Approval must be obtained from the bank before physically accepting the envelope. A customer must be able to make a transfer of money between any two accounts linked to the card. A customer must be able to make a balance inquiry of any account linked to the card. A customer must be able to abort a transaction in progress by pressing the Cancel key instead of responding to a request from the machine. The ATM will communicate each transaction to the bank and obtain verification that it was allowed by the bank. Ordinarily, a transaction will be considered complete by the bank once it has been approved. In the case of a deposit, a second message will be sent to the bank indicating that the customer has deposited the envelope. (If the customer fails to deposit the envelope within the timeout period, or presses cancel instead, no second message will be sent to the bank and the deposit will not be credited to the customer.) If the bank determines that the customer's PIN is invalid, the customer will be required to re-enter the PIN before a transaction can proceed. If the customer is unable to successfully enter the PIN after three tries, the card will be permanently retained by the machine, and the customer will have to contact the bank to get it back. If a transaction fails for any reason other than an invalid PIN, the ATM will display an explanation of the problem, and will then ask the customer whether he/she wants to do another transaction. The ATM will provide the customer with a printed receipt for each successful transaction, showing the date, time, machine location, type of transaction, account(s), amount, and ending and available balance(s) of the affected account ("to" account for transfers). The ATM will have a key-operated switch that will allow an operator to start and stop the servicing of customers. After turning the switch to the "on" position, the operator will be required to verify and enter the total cash on hand. The machine can only be turned off when it is not servicing a customer. When the switch is moved to the "off" position, the machine will shut down, so that the operator may remove deposit envelopes and reload the machine with cash, blank receipts, etc. The ATM will also maintain an internal log of transactions to facilitate resolving ambiguities arising from a hardware failure in the middle of a transaction. Entries will be made in the log when the ATM is started up and shut down, for each message sent to the Bank (along with the response back, if one is expected), for the dispensing of cash, and for the receiving of an envelope. Log entries may contain card numbers and dollar amounts, but for security will never contain a PIN.
Where can i find example or samples of testcases to improve my testcases documentation?
You are Only tester for Onsite client team, this team is on holiday for two day from monday & SIT is started with plan end date is friday in this case if all server,application is crashed then as a tester what will be your approach
Can any one please tell me what is the use of negative test cases when we are giving the invalid input in test data
what is the test plan for ms-word
write the test cases for pen
13 Answers GE, NEDA,
Explain the concurrency testing?
Explain the gray box testing?
Pls write down 3 positive test cases & 2 negative test cases for requirments at the "initiation" & "login" of an ATM machine (format:-Description,test data,methods,set up to test,actions & expected results,any proofs or attachments (optional))
Automation Testing 
