| Title | Check | How evidence is provided |
|---|---|---|
| Java Code | Code is written that fully implements the story. | A link to the commit(s) in the Github history that added this code is added to comments in the story in Pivotal Tracker. |
| Unit Tests | Each new functionality or change must be tested by a Unit test that passes. | A link to the commit(s) that add or change the unit tests. |
| CI passing | When the code and unit tests are written there must be a build on Travis CI that passes. | A link to the passing build. |
| Manual Testing | Manual Tester will run the application and perform the tasks of the user story with a range of valid and invalid inputs. | A link to the test logs. |
| Integration Testing | Each SpringMVC controller method will have automated tests that check the method acts correctly for appropriate inputs. | A link to the commit that added the integration tests. |
| Integration Tests running on CI | The Integration tests pass on Travis CI. | A link to the passing build. |
| Coding Standards Checked | Automatic checking of coding standards is done via gradle and Checkstyle. All code added for the story must adhere to Oracle Standard. | A link to the passing build with the style being checked. |
tabulate the roles and responsibilities that each group member agrees to here. e.g.
| Roles | Chester | Mo | Abdul | Ben | Callum |
|---|---|---|---|---|---|
| Software Developer | x (front end) | x | x | x | |
| Automated Test Writer | x | x | |||
| Build Engineer | x | ||||
| Manual Tester | x | x | |||
| Coding Standards Fixer | x | ||||
| Scrum Master | x | ||||
| Product Owner | x | ||||
| Assessment Lead | x | ||||
| Tech Lead | x | ||||
| Configuration Manager | x |