| Excerpt |
|---|
To be the robust and reliable information system that health care systems demand, we need to be overly vigilant about testing the OpenMRS code. This section contains all testing information including unit tests, continuous integration testing, release testing, and user testing. |
Developers: Contribute Unit Tests
...
To find out where you can help , e-mail the developers mailing list. Download the source code. Add a unit test in /test/org/openmrs. Create one or more tickets and then attach Patches for your unit test to those ticketshave a look at Getting Started as a Developer.
How To Write Unit Tests
- How to write unit tests
- How to write unit tests for modules
- How to write unit tests for the web layer pages
- Unit Testing Conventions
...
We have a Bamboo server set up to run our unit tests after every commit to key branches. On our GitHub repository of OpenMRS core we also use Travis CI which runs your changes to the code and tests on every pull request anyone makes. We also generate test coverage and use coveralls.io to check pull requests to make sure the changes anyone adds are well tested. These checks also run on module repositories within the OpenMRS GitHub organization but it might be that not every module makes use of all the checks.
Visit the JUNIT Junit section of http://ci.openmrs.org to see the latest results of the unit tests in the 1.4.x/1.5.x/..x and trunk branches.
...