TEST CASES FOLDERS STRUCTURE:

Global template

- Salesforce tests
o Home page
o Products page
o Xxxx
Target to reach to have a proper testing in SF. To be carried out
o Xxxx
by an internal tester to ensure the correctness of the system
- End2End tests disregarding any possible rollout
o Placing quotes
o Placing orders
o Xxxxx
o Xxxxx

Rollouts
I’m going to create these now. Include all necessary checks to be done prior to each big testing
- Preparation tests  phase with the countries.

- MESKER These tests are also for internal purposes so we can track and test all
o Specific MESKER functionalities  country specific functionalities before each testing with the clients.
o UAT** 
To be define by the business

- BEST
o Specific BEST functionalities
o UAT

- Country/Project X
o Specific Country/Project X functionalities
o UAT

** UAT is very client oriented. They have to check that the system does what they are
interested in. These are usually very specific scenarios and should always be defined by the
business.
Once we have the test cases, we group them in cycles (= execution instances):

- Sanity tests cycle:

o Includes global template test cases folder. To ensure the global template part
works correctly

- Country/project X Integration tests:

o Includes Preparation tests
o Includes global template test cases folder
o Includes Specific Country/Project X functionalities test cases folder

- Country/project X UAT tests:

o Includes Preparation tests
o Includes UAT test cases folder

This is a basic idea, more cycles could be created mix&matching the different tests in the
different test cases folder.

Test cycles can also have a folder structure, so we can structure them by projects:

PROJECT X:

- Sanity tests cycle

- Integration tests cycles
o IT1
o IT2
o …..
- UAT
o UAT1
o UAT2
o …..