... | ... | @@ -33,8 +33,8 @@ We would take turns editing files to add new features that were helpful because |
|
|
|
|
|
We had weekly meetings for talking about which direction we were heading and what we have accomplished. Each person would give a brief rundown of things they implemented and how. If anything was deemed to not meet the standards set we would add an issue to the Issue Board on GitLab to be tackled by the person assigned.
|
|
|
|
|
|
|
|
|
|
|
|
## Acceptance Testing
|
|
|
Before we know our product is ready to be released, we have multiple stages of testing by our stakeholders', user-group, and any friends or family we can rope into it. Giving them control and asking them to explore the product on their own, then later guided, to see if they are able to understand how the application works without a given explanation. We also ask them to try and break the application so we can find bugs that might not have appeared during internal testing.
|
|
|
|
|
|
|
|
|
|
... | ... | |