-
Notifications
You must be signed in to change notification settings - Fork 4
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
reprostim-*capture -- start adding tests via ctests framework #74
Comments
vmdocua
added a commit
that referenced
this issue
Feb 20, 2024
5 tasks
vmdocua
added a commit
that referenced
this issue
Feb 20, 2024
vmdocua
added a commit
that referenced
this issue
Feb 20, 2024
vmdocua
added a commit
that referenced
this issue
Feb 20, 2024
vmdocua
added a commit
that referenced
this issue
Feb 21, 2024
vmdocua
added a commit
that referenced
this issue
Feb 21, 2024
vmdocua
added a commit
that referenced
this issue
Feb 21, 2024
vmdocua
added a commit
that referenced
this issue
Feb 21, 2024
vmdocua
added a commit
that referenced
this issue
Feb 21, 2024
vmdocua
added a commit
that referenced
this issue
Feb 24, 2024
vmdocua
added a commit
that referenced
this issue
Feb 24, 2024
vmdocua
added a commit
that referenced
this issue
Feb 27, 2024
vmdocua
added a commit
that referenced
this issue
Feb 27, 2024
vmdocua
added a commit
that referenced
this issue
Feb 27, 2024
vmdocua
added a commit
that referenced
this issue
Feb 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
adding them to workflow makes testing CI specific. We best encode tests using standard way, and since cmake is to be used here,
ctest
sounds like a logical way to organize them.The text was updated successfully, but these errors were encountered: