qa-of-code-guidance
qa-of-code-guidance copied to clipboard
best-practice-and-impact
Guidance for quality assurance of code for civil service researchers and analysts.
Link is dead for [PATRICK’S SOFTWARE BLOG](https://www.patricksoftwareblog.com/setting-up-gitlab-ci-for-a-python-application/)
Consider adding [poetry](https://python-poetry.org/) and removing Travis from Tools page. Consider adding a note to say that Rgovcookiecutter is still quite early in development
Include solutions for how to rebase code in the merge conflict resolution, version control section. https://www.atlassian.com/git/tutorials/rewriting-history/git-rebase
The book uses an Open Government License which explains how the guidance given can and cannot be used. To find this information, users must follow the GitHub icon to the...
Consider creating an issue template to gather key information needed when adding a tool to the book
Testing page currently lacks detail on integration and end to end testing. Page should cover what the purpose of these tests is, when to write them and what to think...
De-emphasise this section as better practice is to use dedicated config files.
When looking at #122 I discovered that the chapter is written as a tutorial and needs to be reframed to guidance.
Higher checklist states: The extent of analytical quality assurance conducted on the project is clearly documented. We should provide further context to this: What is expect to meet this point,...
Metadata
Owner
Metadata
Guidance for quality assurance of code for civil service researchers and analysts.