...
- We need to get better at integration with "bundled" modules, in order to reduce potential problems for release testing.
- Automated testing will catch what we know might be problems, but user testing will identify unanticipated errors.
- We would like to reach a point where CI is doing more integrated builds for testing (and release management, too).
- How can we do continuous higher-level integration test that includes bundled modules?
- Can we better automate building of the ?OpenMRS Appliance?
- TODO Burke will get some discussions about these topic started on the mailing lists.
- TODO Justin will give Wyclif a crash course on BIRT Reporting Module so Wyclif can write tests for it. They will likely use James Arbaugh's test report.
1.8 Release Testing
- Performance testing results are available at http://ci.openmrs.org/ - currently testing against 1.7.0 RC. Anyone who has the ability to work on JIRA issues in TRUNK is able to start a test run. TRUNK project "approvers" can edit the test configuration in Bamboo/CI.
- TODO Wyclif is finishing up some of the tests. The 1.8 Top Ten page will be updated to correlate the top 10 to the specific tests being run.
- TODO Darius will work to expose the build number via WebDriver.
- TODO Burke will work on reporting test data from the XML results at http://errors.openmrs.org/reports/
- TODO Darius is taking the test data set and upgrading it to 1.8 and will send it to Michael who will get the trunk build set up for testing.
- TODO Someone
will configure the tests to run 10 iterations for every "build" that CI runs.
...