OpenMRS 1.9 Module Testing

We'd like to test module compatibility with OpenMRS 1.9 before the final release. This will help ensure a smoother upgrade for everyone.

If you're a module developer, or your site relies on a module, please test it against the 1.9 Alpha release and post your feedback below. The alpha standalones can be downloaded from http://sourceforge.net/projects/openmrs/files/prereleases/OpenMRS_1.9.0_Alpha/ . The login is admin , password Admin123 .

If your module has been mavenized, you should attempt to run your module unit tests against the 1.9 Alpha release. This can be done by changing the "openMRSVersion" property defined in the main module pom to "1.9.0-alpha" and then running a clean install. You can modify the property directly in the pom, or you can specify it as a command line parameter: "mvn -DopenMRSVersion=1.9.0-alpha clean install". Note that if you were previously building against a version of OpenMRS prior to 1.8.0, you'll have to (temporarily) modify your openmrs dependencies in your poms as noted here. Also, if you have any test data sets defined in your module you may have to (temporarily) modify any concept_name entries to include the new locale_preferred property added in OpenMRS 1.7.0.

The initial list of modules includes all of the bundled modules, plus the most downloaded modules. You may add any other modules that you use.

In the last column, please give your opinion about whether the module is ok to release. Yes means you found no problems. Maybe - there are issues but your site can work around them. No - the module won't work after upgrade.

Bundled Modules

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

Atlas Module 1.0

HTML Form Entry 1.7.3

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No
~jriley	saved the default form with and without a second provider field made a few encounters of each kind	The form saved. There's no support for multiple providers or encounter roles yet - as expected. Old forms will continue to work.	HTML-225 - Getting issue details... STATUS HTML-226 - Getting issue details... STATUS HTML-227 - Getting issue details... STATUS	Yes.
Mark Goodrich	Ran unit tests against 1.9.0-alpha	See tickets to the right for info on failing unit tests NOTE: this is still a work-in-progress as there are still several failing unit tests that need to be researched	HTML-231 - Getting issue details... STATUS HTML-232 - Getting issue details... STATUS HTML-233 - Getting issue details... STATUS HTML-234 - Getting issue details... STATUS HTML-235 - Getting issue details... STATUS (jira:HTML-236}	Maybe

Xforms 4.0.8

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

HTML Widgets 1.5.7.1

Your name	What features did you test? How?	Results	Ok to ship? Yes/Maybe/No
~jriley	stepped through all the widgets on the test page /module/htmlwidgets/demonstration.form	they all worked	yes

Reporting Compatability 1.5.4.1

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

Reporting 0.6.2

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

Serialization Xstream 0.2.5

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

Logic Module 0.5

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

Popular Modules

Patient Flags 1.3.2-r23863

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No
Mark Goodrich	Ran all unit tests against 1.9.0-alpha. Loaded module into 1.9.0-alpha standalone and created a simple SQL flag and a simple Groovy flag.	All unit tests passed successfully. Was able to create and preview flags. Flag appeared properly in overview section of Patient Dashboard, but did NOT display in the header of Patient Dashboard. Someone with a better understanding of Logic should test out a Logic flag.	FLAG-6 - Getting issue details... STATUS	Probably

Form Entry 4.5.9.4

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

Groovy 2.0.4

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

Metadata Sharing 0.9.0.2

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

Birt Reports 2.5.2.1

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

Rwanda Primary Care Module 2.0.3

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

Form Import Export 1.6.0

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

Clinical Summary Module 2.0

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

Remote Form Entry 2.9.6

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

REST Module 1.4.4.2

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

Double Entry Reconciliation 1.6.4

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No

ID Generation 2.1

Your name	What features did you test? How?	Results	Ok to ship? Yes/Maybe/No
~jriley	* Created an id source with options Local Identifier Generation, using chars 0-9, length 7 * Created a patient identifier type that used the source, allowed autogeneration, Luhn validation scheme * Added a patient, selected the new identifier type, clicked generate	New ID was generated	Yes

Address Hierarchy 2.1.1

Your name	What features did you test? How?	Results	Ok to ship? Yes/Maybe/No
~jriley	Imported the hierarchy csv file I used in 1.8, assigned columns to address fields, and created a couple patients	Works as before	Yes

Blank Template

Copy and paste this to add another module.

Your name	What features did you test? How?	Results	JIRA tickets	Ok to ship? Yes/Maybe/No