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.

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

Set up CI #51

Open
scottwittenburg opened this issue Jan 12, 2021 · 2 comments
Open

Set up CI #51

scottwittenburg opened this issue Jan 12, 2021 · 2 comments

Comments

@scottwittenburg
Copy link
Collaborator

This could be a very involved or quite simple issue, depending on what we intend to do in CI. At a minimum, we should decide on client/server code styles we want to enforce, and at least make sure contributors are adhering to those.

More involved would be deciding how we want the project to be tested, choosing and implementing a testing framework, and writing tests to cover the application code.

@aashish24
Copy link
Contributor

@scottwittenburg CI for MIQA would be awesome. I would start with perhaps just build checks? And later add on testing and coverage. What do you think?

@scottwittenburg
Copy link
Collaborator Author

Good idea, I think build checks is a great place to start.

@dzenanz dzenanz added this to Todo: Low Priority in Sprint Board (4 week) Feb 25, 2021
@aashish24 aashish24 moved this from Backlog (Accepted) to Triage (Needs Grooming) in Sprint Board (4 week) Mar 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Sprint Board (4 week)
  
Triage (Needs Grooming)
Development

No branches or pull requests

2 participants