marklogic / marklogic/marklogic-contentpump
Separate unit and integration tests
Open
Nobody has claimed this yet.
bug
minor
mlcp
verify
- Dominant language
- Java
- Stars
- 37
- Forks
- 32
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 12
Description
The current set of tests function mostly as integration tests that require a live instance of MarkLogic, and take ~15 minutes to run.
- Unit tests should run quickly, and not rely on external systems.
- Mock objects should be used in place of a live database for unite tests, or the test should be moved into an integration test suite.
It would be helpful, and make it easier for contributors, if the tests and build were organized to facilitate separate execution of unit tests and integration tests. This would also make it easier to integrate with CI services, such as Travis CI and/or Circle CI without having to exclude the test phase.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.