2011-05-31 Development Sprint

Owned by Ben Wolfe
Last updated: Jun 02, 2011 by raffVersion comment
2 min read

General Info

Topic: Automated Release Testing
Lead(s): Ben Wolfe
Date: May 31st - June 12th 2011
Kickoff Meeting: 10am ET, Monday May 31st (find your timezone)

Group Chat

via IRC on the #openmrs-sprint channel on freenode.

Use this channel for ALL debugging and random questions having to do with the sprint. Please avoid direct messaging to personal contacts. If you have a question, someone else probably does too, and our geographically distributed community benefits from public group discussion.

About

The goal of this sprint is to create a suite of unit tests that test web layer functionality.

Initial testing should focus on automating the Rudimentary Testing within /wiki/spaces/docs/pages/25468482

All code should be worked on in this branch: http://svn.openmrs.org/openmrs/branches/webapp-testing

1 minute overview

The goal of the release testing is to create a set of "stories" about what we want to test.  Example story.

There is then a java class that works uses that story template to execute the test.  Example java and Example step reading the template.

Webdriver, jetty, and selenium are used behind the scenes to script and execute the actual steps/test

Running the tests

First give maven more memory to work with:
export MAVEN_OPTS="-Xmx1024m -Xms256m -XX:MaxPermSize=256m"

To run all tests:mvn clean integration-test -DskipTests -P integration-test
To run tests against a pre-defined db (and specific tests):mvn clean integration-test -DskipTests -P smoke-test -Dtest=CreateAnEncounter

How to Participate

Add your name to the list on this wiki page (with any comments about your availability). If you want to join after the sprint has started just join the IRC channel mentioned above and say hello.

The general process:

  1. Pick a ticket from the available tickets in the top-left of the dashboard.
  2. If you have any questions about the ticket, ask on the group irc chat
  3. Do the ticket
  4. Either:
    1. (preferred) Commit the code to the branch and open a new "post commit" review in Crucible.
    2. (not preferred) Attach a patch and click "Request Code Review" or Commit code and click "Committed Code"

Participants

Please try to attend the kickoff meeting (see above for timing).

Tickets and Work Items

See this sprint's JIRA dashboard

All tickets with fix version of "Sprint 1" in the APPTEST project.

Other Resources