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

Separate Continuous Integration Tests #9

Closed
dekuenstle opened this issue Jan 2, 2021 · 0 comments
Closed

Separate Continuous Integration Tests #9

dekuenstle opened this issue Jan 2, 2021 · 0 comments

Comments

@dekuenstle
Copy link
Collaborator

dekuenstle commented Jan 2, 2021 •
edited

Currently, we have one big test workflow. We should separate it to multiple workflows to keep it more maintainable, making the source of fails more obvious, and probably even speeding up.

I would suggest the following workflows:

  • Unittests (Core)
  • Unittests (wrapper: R and Octave bridges)
  • [probably: Unittests (GPU)]
  • Code Style
  • Documentation

This might be a nice issuefor someone interested in getting started with Github Actions + test automation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dekuenstle