Answers to this exercise will vary as different people have different experiences.

The following are likely elements of the system together with a possible rationale for choice of test case level.

Concrete test cases

• Legal concerns – e.g. distance selling regulations
• Credit card issues (audit / legal – PCI security standards)
• Security – to protect the brand and to meet the BS7799 security standard.
• The new functionality – have documented requirements, it’s new so need to show it works and likely to repeat the tests (retesting / regression testing).
• Accessibility – show it meets the disability discrimination legislation.
• Usability – protect the brand, ensure maximum chance that customers can easily purchase and repeat, show meet standards.

Logical test cases

• Existing functionality – it is already working so some high level testing to give confidence there are no regression defects. Also, as there are few documented requirements, logical test cases are an appropriate choice.
• The new functionality – broader scope than concrete tests, included to supplement the concrete tests.
• Usability – to see how the users do things, allow them to do things their own way.
• Use them to help define and improve the requirements – company does not appear to have a strong history of writing requirements.
• Low risk / low priority areas – also because of the lack of time.
• Branding – given the time pressure we cannot spend a lot of time checking the branding but this is important to consider. Logical test cases will be a quicker and cheaper way to focus on the most important or most visible branding.