Closed ivanperez-keera closed 6 months ago
Change Manager: Confirmed that the issue exists.
Technical Lead: Confirmed that the issue should be addressed.
Technical Lead: Issue scheduled for fixing in Copilot 3.19.
Fix assigned to: @ivanperez-keera .
Implementor: Solution implemented, review requested.
Change Manager: Verified that:
uTypeType
, which cannot be tested due to being part of an existential type (it's necessity is being discussed in #484). The modules Copilot.Core.Operators
and Copilot.Core.Spec
and Copilot.Core.Expr
only contain datatype definitions, so they do not need to be tested.Change Manager: Implementation ready to be merged.
Description
The test coverage of
copilot-core
is currently reported at 25% by Hackage. This is very low.Although there are exceptions to what we can test (record fields of existential types) or should tests (proxies, automatically generated constructors and accessor functions), the coverage of our tests should be higher and anything that is not tested should be documented.
Type
Additional context
None.
Requester
Method to check presence of bug
Not applicable (not a bug).
Expected result
All top-level functions that are not automatically generated by the compiler are tested, except where testing them is not possible or for code that is automatically generated (constructors, record accessor functions). Anything not tested is documented.
Desired result
All top-level functions that are not automatically generated by the compiler are tested, except where testing them is not possible or for code that is automatically generated (constructors, record accessor functions). Anything not tested is documented.
Proposed solution
Add tests for all definitions in
Copilot.Core.Type
andCopilot.Core.Type.Array
, except record accessor functions.Further notes
None.