Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
Child pages
  • Add UI Unit Testing Design
Skip to end of metadata
Go to start of metadata

This work was superseded by UI testing of the reference application

 

Background

We have many ?Unit Tests for the api and web layer.  However, these only test java code (api methods or controller methods), no jsp or javascript is tested.  There are many things in the webapp that change but also a lot that stay the same.  We need a suite of tests that make sure some of the basic functionality (the part that stays the same) doesn't break from release to release (and really from commit to commit).

There is a suite of performance testing web driver tests here: http://svn.openmrs.org/openmrs-contrib/performance-benchmark/  See the readme.txt for how to execute them.  You can use these as a jump start on how to integrate webdriver and ui tests into trunk.

Requirements

The Release Process wiki page links to the rudimentary testing process that must be done before each alpha/beta release.  These ideally should be some sort of automated unit test (similar to but not necessarily the same as web driver)).

The minimum tests that need to be run are on that Testing Releases wiki page. 

The tests should be in trunk so that any developer can run them (regardless of OS)

A final piece of this is to work with ?Michael Downey to set up a CI project 

Assigned Developer(s)

?Zabil C.M etc

Mentors and Other Interested Parties

Mentor: [?Darius Jazayeri, Ben Wolfe|~bwolfe]

Design

To be completed by developer and mentor(s)

  • No labels