| 3 |
short release cycles |
3 releases can be seen in GitHub |
| 3 |
workload is spread over the whole team (so one team member is often Xtimes more productive than the others... |
https://github.com/kingan1/application-tracking-system/graphs/contributors |
| 3 |
Docs: why: docs tell a story, motivate the whole thing, deliver a punchline that makes you want to rush out and use the thing |
Readme.md, docs/app.md, test_app.md |
| 3 |
the files CONTRIBUTING.md lists coding standards and lots of tips on how to extend the system without screwing things up |
have contributing.md file |
| 3 |
Docs: doco generated , format not ugly |
Readme.md, docs/app.md, test_app.md |
| 3 |
evidence that the whole team is using the same tools (e.g. config files in the repo, updated by lots of different people) |
commits are across the codebase, in GitHub actions |
| 3 |
evidence that the members of the team are working across multiple places in the codebase |
commits are across the codebase. |
| 3 |
Docs: what: point descriptions of each class/function (in isolation) |
in Readme.md, docs/app.md, test_app.md |
| 3 |
Number of commits: by different people |
https://github.com/kingan1/application-tracking-system/graphs/contributors |
| 3 |
issues are being closed |
https://github.com/kingan1/application-tracking-system/issues 23 issues closed |
| 3 |
issues are discussed before they are closed |
in issue comments ex: kingan1#2, kingan1#2 |
| 3 |
Use of syntax checkers. |
Super Linter in GitHub actions |
| 3 |
Issues reports: there are many |
in GH |
| 3 |
Use of code formatters. |
Super Linter in GitHub actions |
| 3 |
Use of style checkers |
Super Linter in GitHub actions |
| 3 |
Docs: short video, animated, hosted on your repository. That convinces people why they want to work on your code. |
in README.md |
| 3 |
test cases exist |
in test_app.py |
| 3 |
Use of code coverage |
in GH |
| 3 |
other automated analysis tools |
Super Linter in GitHub actions |
| 3 |
test cases:.a large proportion of the issues related to handling failing cases. |
in GH |
| 3 |
test cases are routinely executed |
GitHub actions |
| 3 |
Documentation describing how this version improves on the older version |
Readme.md |
|
This version is a little(1), some(2), much(3) improved on the last version. |
Tutor's assessment. |
|
Total |
|