How to Write Test Plan for Boundary Value Testing, Decision Table Testing and Equivalence Class Testing

1. Solution:

 Variable Description Units Range CD Call Duration hour:min:sec 0 – 30 hours CST Call start time JulianDay:hour:min:sec 1<=JulianDay<=366 0<=hour<=23 0<=min<=59 0<=sec<=59 CET Call end time JulianDay:hour:min:sec (same as for CST) Cost Charge for call US Dollars and cents max Cost = \$179.00

Equivalence Class Testing:

EC Testing is once you have variety of test things (e.g. values) that you just need to test however due to value (time/money) you are doing not have time to test all of them. So you group the test item into category wherever all things in every category are alleged to behave precisely the same. The idea is that you just solely have to be compelled to test one among every item to create certain the system works.

There is a danger of using EC Testing that’s seldom mentioned within the testing books however is incredibly necessary to recollect. Just because 2 items/values are alleged to be within the same category and behave constant, doesn’t mean they do behave the same.

That means that simply because you take a look at one worth within the category that everyone values within the category behave constant. They were alleged to all work constant however they did not actually. Therefore testing only one worth during a category is nice, however not good enough. EC Testing could be a sensible tool, however it isn’t fool proof and use caution with it. If take a look at cases are low-cost and quick (like automation), test more, or why not take a look at all.

Critique of Boundary Value Testing:

BV Testing is after you arrange to test the values on the edge of every class you have got identified. The idea is that the majority defects is round the edges of a class.

The fact that you simply ought to use BV Testing proves that EU Testing is imperfect since you take a look at over one worth of every category. It is simple to use when using values like integers. However what’s a boundary worth of sophistication of phones models or browsers versions?

The boundary values of a category is usually supported the specification of however the system ought to work. This is often all smart and well however most systems contain boundaries that aren’t explained in any description and you ought to search for yourself.

Test Cases:

• Check if the value added services are enabled or disabled.

• Check if the plan downgraded is selected by is billing system.

• Check if the total amount is accurate and mapped to the services offered.

• Check if the number of calls are valid by matching them to customer records.

• Check if the tariff plan is properly calculated for billing cycle.

• Check if the prepay system has accepted additional money for future billing.

• Verify if the floating point balance is carried forward into the next bill.

• Verify if the card transaction has been successful in payment terminal.

• Verify if the bill is paid by customer and it reflects in the system.

• Verify if the prepay balance is used in the current billing.

• Verify if the customer has chosen card or cash transaction.

Testing Procedure:

This test satisfies User Story #1 (“Check if the value added services are enabled or disabled”)
Author:

 Case Action Expected Actual Pass/Fail 1
Performed by:

This test satisfies User Story #2 (“Check if the plan downgraded is selected by is billing system”)
Author:

 Case Action Expected Actual Pass/Fail 2

This test satisfies User Story #3 (“Check if the total amount is accurate and mapped to the services offered”)
Author:

 Case Action Expected Actual Pass/Fail 3
Performed by:

This test satisfies User Story #4 (“Check if the number of calls are valid by matching them to customer records”)
Author:

 Case Action Expected Actual Pass/Fail 4
Performed by:

This test satisfies User Story #5 (“Check if the tariff plan is properly calculated for billing cycle”)
Author:

 Case Action Expected Actual Pass/Fail 5
Performed by:

SHARE