Currently to create acceptance tests we follow this process:
1) Create a stub with high level details
2) Finalize details over dev process
3) Copy test and change per enviornment
4) ANy changes/gaps discovered need to either change one and re-copy or change every test instance

1) Create root test (aggregate)
2) Create environment testing (preferably through some configured one click action, would be linked to root any change in root would reflect in these tests)

Comments