-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a basic test infrastructure #86
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@regularfry This PR establishes a very clean and easy-to-follow pattern. It would be good to get it merged. I've made some comments and suggestions for changes to ensure it matches the existing style of writing. Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
…to README Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
Github markdown and the markdownlint tool we're using disagree about what a code block in a footnote should look like. This patch removes the footnote and moves the content inline. Signed-off-by: regularfry <[email protected]>
Signed-off-by: regularfry <[email protected]>
Head branch was pushed to by a user without write access
Description
This PR adds
make
tasks for running tests.Context
This issue says that we're out of alignment with wider policy in the sense that we're applying stricter rules than government policy requires.
There are two ways to solve this: we can either loosen our rules, or make them easier to comply with. From the point of view of the test statuses we require in the quality framework here, this does the latter.
Specifically it allows the user of the template to put scripts into
scripts/test
for running the various types of test required by thesoftware-engineering-quality-framework
which, until they are implemented, will output a warning to the console (but do not fail).Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.