-
Notifications
You must be signed in to change notification settings - Fork 13
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
Initiate unit tests of the source code #108
Comments
Hi Tom, For others, if anyone is interesting in starting work on this, please let me know. Thank you. 73, Mike W7SST |
@tekenny I am about to start checking in the parser and the SS Contest code. I was wondering if I could include you on these Unit Test code reviews. I would like your input. Thank you. 73, |
- part of Issue #108 - Adds a group file, MRCE.groupproj containing both MorseRunner and UnitTests.dproj - built using DUnitX - a goal would be that anything going into the Util/ directory would be unit tested.
Starting with v1.85 development, several units now have corresponding Unit Tests. The goal should be anything units added to the new The unit tests are stored in a single directory I will leave this Issue open because there is still more work to do. Next steps would be to find other packages that can be unit tested (see Task list above) |
Description
Where possible and appropriate add unit tests of the source code.
Why - unit testing helps to improve quality by identifying failures as a result of changes to the code base.
Steps To Reproduce
None - no unit test currently exist
Expected behavior
Availability of a automated test suite to help ensure quality
Actual Behavior
Ability to run a test suite
Reproduces how often
Always
Version information
Additional context
TASKS
Can you help?
Please let us know if you are available to help. (replace '[ ]' with '[x]' to affirm)
The text was updated successfully, but these errors were encountered: