Skip to content
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.

Sign up for GitHub

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

Jump to bottom

testing #605

Closed
inghylt opened this issue Jun 1, 2021 · 3 comments
Closed

testing #605

inghylt opened this issue Jun 1, 2021 · 3 comments
Assignees
@inghylt
Labels
CII Best Practice epic

Comments

@inghylt
Copy link
Contributor

inghylt commented Jun 1, 2021

CII Best Practice:

  • The project MUST use at least one automated test suite that is publicly released as FLOSS (this test suite may be maintained as a separate FLOSS project). The project MUST clearly show or document how to run the test suite(s) (e.g., via a continuous integration (CI) script or via documentation in files such as BUILD.md, README.md, or CONTRIBUTING.md)
  • A test suite SHOULD be invocable in a standard way for that language
  • It is SUGGESTED that the test suite cover most (or ideally all) the code branches, input fields, and functionality
  • It is SUGGESTED that the project implement continuous integration (where new or changed code is frequently integrated into a central code repository and automated tests are run on the result)
  • The project MUST have a general policy (formal or not) that as major new functionality is added to the software produced by the project, tests of that functionality should be added to an automated test suite.
  • The project MUST have evidence that the test_policy for adding tests has been adhered to in the most recent major changes to the software produced by the project.
  • It is SUGGESTED that this policy on adding tests (see test_policy) be documented in the instructions for change proposals.

As a developer, I would like to have test validating my code, so that I know that changes I make don't create bugs that are missed during PR reviews

As a user, I would like to have test validating the code, so that I know that the software I use is functional and that I use valid data
@mihai-sysbio
Copy link
Member

The testing framework cypress is implemented - a first test in written at frontend/cypress/testing. To run the tests see the dev docs

Potentially use https://chrome.google.com/webstore/detail/cypress-recorder/glcapdcacdfkokcmicllhcjigeodacab

@mihai-sysbio mihai-sysbio mentioned this issue Aug 31, 2021
Merged
@mihai-sysbio
Copy link
Member

@e0 mentioned these frameworks in #673 (comment) :

@mihai-sysbio mihai-sysbio changed the title Add testing testing Nov 19, 2021
@inghylt inghylt self-assigned this Aug 11, 2022
@inghylt
Copy link
Contributor Author

inghylt commented Aug 12, 2022

Issues
#849
#1082
#1083

are actionable issues that cover what we have left to fulfill, closing this epic

@inghylt inghylt closed this as completed Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@inghylt inghylt

Labels
CII Best Practice epic
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mihai-sysbio @inghylt