You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's possible that passing the IPM context to the unit test manager could require an IPM change - likely just adding a line to pass the package name as a user param. Could also be achieved through a custom lifecycle class within this package (which we'd want to exclude).
Probably makes sense to hold this until after the IPM rename is done.
The text was updated successfully, but these errors were encountered:
Fixes#43Fixes#20
Partially addresses #28 by adding doc on how to run via IPM - there's still more we could do to make the support more automatic but that'll be left as a future enhancement.
When used in an IPM context we should automatically determine which classes to cover (without requiring coverage.list). Documentation in this GitHub repo should cover how to enable that as well as incorporate relevant content from https://community.intersystems.com/post/unit-tests-and-test-coverage-intersystems-package-manager .
It's possible that passing the IPM context to the unit test manager could require an IPM change - likely just adding a line to pass the package name as a user param. Could also be achieved through a custom lifecycle class within this package (which we'd want to exclude).
Probably makes sense to hold this until after the IPM rename is done.
The text was updated successfully, but these errors were encountered: