This repository has been archived by the owner on Dec 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 32
Ambiguous testing documentation process #57
Labels
Comments
Let's draft up CONTRIBUTING.md to give others an idea of what they should and shouldn't do with examples. |
Job #57 is now in scope, role is |
@Biboran I will work on that. |
You can't do that, unless you have one of these roles: |
@0crat waiting |
@driver733 The impediment for #57 was registered successfully by @driver733/z |
abdulowork
added a commit
that referenced
this issue
Feb 27, 2018
#57 - Added CONTRIBUTING.md with info about tests and PRs.
The PR has been merged. |
Order was finished, quality was "acceptable": +30 points just awarded to @driver733/z, total is +535 |
The job #57 is now out of scope |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We need to clarify and document somewhere the framework for how we expect tests to be written.
The text was updated successfully, but these errors were encountered: