-
Notifications
You must be signed in to change notification settings - Fork 30
Unit-Tests #68
Copy link
Copy link
Open
Labels
HIGH PRIORITYIssue is extra high priorityIssue is extra high priorityScheduledScheduled to be worked on or is already in progressScheduled to be worked on or is already in progressbugSomething isn't workingSomething isn't workingdocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestfeature requestSomething is wantedSomething is wantedhelp wantedExtra attention is neededExtra attention is neededteam core
Metadata
Metadata
Assignees
Labels
HIGH PRIORITYIssue is extra high priorityIssue is extra high priorityScheduledScheduled to be worked on or is already in progressScheduled to be worked on or is already in progressbugSomething isn't workingSomething isn't workingdocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestfeature requestSomething is wantedSomething is wantedhelp wantedExtra attention is neededExtra attention is neededteam core
as it currently stands the repository is not backed by unit-tests!
We should invest some time into looking into which unit-test framework we want, and implement at least basic test such that subsequent ci runs can detect code that breaks the previous code-base
https://github.com/onqtam/doctest
https://github.com/catchorg/Catch2
https://www.boost.org/doc/libs/1_73_0/libs/test/doc/html/index.html
Additionally we should decide if we want advanced tools for our ci system like code-cov to asses the quality of the unit-test in addition to running them