-
First of all, thank you for writing this very neat proposal!
I thought I'd make a suggestion to include unit tests with more code coverage. That way it would be easier to check that everything in the…
-
The test coverage is inadequate. We need to increase it, particularly add coverage for edge cases and erroneous situations.
-
```
--------------------------------|----------|----------|----------|----------|-------------------|
File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s …
-
Current version of `covr` fails to parse some "invalid multibyte characters" in the dictionaries. Need to figure out a workaround to get tests to work.
-
Most of (all) the code isnt tested yet. To make sure everything works alright the code has to be tested.
And code coverage would be cool aswell - especially for the cool badge on the README!
-
Right now, the library is completely untested, and although some bugs have been identified and patched from using Pract in my own game, full coverage would be ideal before publicizing this library and…
-
The repository is painfully lacking in test coverage. I'm currently working on a PR that will add some basic unit test coverage so that a CI pipeline can be built, however I'd like to have all current…
-
rimio updated
3 years ago
-
Once we've moved the tests from Travis (https://github.com/FAIRDataPipeline/data-registry/issues/68), we should start improving the tests due to all the recent changes.
-
Add tests for any parts that are nontrivial and/or can be tested with reasonable effort.
- Quasiquote system
- Corner cases
- Multiple macro invocations in the same `with`
- Decorator ma…