Need to just refine our process a bit because it's becoming too much of a burden for acceptance testing. This might only be in place until product launch and then we can review and revise. All acceptance testing will be done on the staging server.
- Easier acceptance makes it happen quicker, preventing blocked stories
- Easier merges into master since we won't get too far behind
- Won't have to deal with features not working due to missing dependencies on Wes/Marshall's machines
- Create a branch for each new feature.
- Write the tests, write the code.
- When ready to deliver, merge into master, "Finish" story in tracker
- Deploy to staging server: cap staging deploy
- "Deliver" story in tracker
- Remove branch.
All acceptance testing will be done by Wes/Marshall etc. on the staging server. Please limit your testing to exactly what the story is about. Rejecting a story because of an unrelated item is not helpful. Create a chore or bug instead.
- Load up tracker and open up a story that needs accepting
- Read the description and comments
- Login to staging server at http://staging.emgateway.ca
- Test to make sure story passes.
- If it does not meet the technical requirements of the story, reject with very specific comments.
- Accept if it meets the requirements.
- Repeat