gardners/2014SE3 — pull request #184 by Silentki113r (2014-06-27 08:29:37+00:00)
Title: Prac 6

Website Payment System – Scha0147

Design:

This test plan is built around conducting payment on a website. This system allows customers to make purchases online and is quite a core function of the website.

System Stages In System:

```
Enter Payment Credentials:
- Card holder name.
- Card Number.
- CCV.
Communication with Bank:
- Valid card holder.
- Valid amount for payment available.
Order Placed:
- Confirmed order.
- Money received.
- Order lodged.
```

Risks and Severity:

Customer can pay for item and item order is not lodged.
Order is lodged, no payment received.
Invalid funds.

Worst risk being:
Customer can pay for item and item order is not lodged. This can most certainly result in bad reputation.

Testing Methods:

Integration Testing:

Make sure communications can be made to all banks for purchasing. Also clearly establish cards that are and aren’t accepted (AMEX etc…). Deny all those who aren’t accepted.

Stress Testing:

Lodge many orders at once, including orders which should be invalid, to test systems capabilities and functionality.

Usability Testing:

Allow flexibility for customers: provide alternate methods of payment.

Recovery Testing:

If something breaks, it needs to be identified and fixed quickly to allow business to continue quickly. How is problem identified.

End to End Testing:

Can system cope with a basic operation: purchase something.

System Testing:

Does system meet requirements?

Three most important:
End to End:
If the system cant cope with a function its primary purpose is to do then the system is useless.

Stress Testing:
Real world scenarios may involve many people ordering and purchasing at one, system needs to be able to handle this.

Integration Testing:

Needed for making sure system works with others and eliminates many problems that may arise.

Three lesser important:

Recovery Testing:
Still important, if system goes down trading stops, problem needs to be identified and fixed quickly.

System Testing:
Need to meet requirements.

Usability Testing:
Flexibility for user.