testing.md 1.71 KB
Newer Older
bgm's avatar
bgm committed
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
This file outlines what should be witnessed in manual testing (WIP)

1) Membership discounts - no auto-discount

<img src='/docs/images/MembershipDiscountCode.jpg'>

<b>Back office forms</b>
- When renewing a discount box is visible if the renewal type is eligible for a discount.
- The discount box is visible for all new membership backoffice forms.

<img src='/docs/images/RenewBox.jpg'>

- Provided the code is entered and apply clicked before selecting a membership type the discount is applied
- Clicking 'Save' creates a membership with a suitably discounted contribution.
- there is only one financial trxn row.

<b>With price set</b>
- The applies and alters the price as long as it is applied AFTER the price set is selected. Before has no effect
- Clicking 'Save' creates a membership with a suitably discounted contribution.
- there is only one financial trxn row.


<b>Front end forms</b>
- the discount code box is offered when the discount is available - both when configured via price set and when not
(visibly) configured by price set.
- on continuing the confirm page shows the discounted amount
- the contribution is for the discounted amount
- one financial trxn row.


@todo the way 'apply' interacts backoffice (described above) is pretty wierd.
@todo currently auto-discounts are only applied back end for price sets. Changing the type in the renewal does not
change visibility or otherwise of the discount box.
@todo single financial trxn row is possibly incorrect - a JIRA exists on this.

2) Membership discounts - auto-discount

<img src='/docs/images/MembershipAutoDiscount.jpg'>

Much the same tests as above - discounting did not appear to work on back office renewals (before or after changes) but was otherwise successful