Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
Lead (Product Owner): Joseph Kaweesi
Developer Lead: Joseph Kaweesi
Known Contributors Assigned: OpenMRS community
Tickets to be tested:
Testing server URL: http://uat01.openmrs.org:8080/openmrs
User Name: admin
Tickets to be tested: 1.11 Release tickets on target for testing
Source Code: https://github.com/openmrs/openmrs-core/tree/1.11.x
Sprint Start Date: Thursday, 14/08/2014 19:00 UTC (Second Iteration)
Sprint End Date: Thursday 28/08/2014 19:00 UTC (Second Iteration)
We have at-least 150 tickets left that we are to test so we confirm their fixes before they are included in the OpenMRS 1.11 release, We hope that this work will be effectively done by the OpenMRS community.
A ticket can be tested by more than one person to get more reliable feedbacks, feedback on specific tickets will be done at the ticket pages.
Since we are keeping records to appear in our statistics, a person is considered to have tested a particular ticket when his/her work is well documented on jira, via comments or/and edited labels to either pass or fail a ticket, we encourage all of you to take place since as i mentioned we have goodies to offer:
3. Lastly; listing all the testers/contributors in the 1.11 release notes.
Register for an (OpenMRS Id ).
Begin straight away by checking out the list of tickets to be tested , you don't need to assign your self of any of them to do the testing.
After targeting any ticket, and visiting its url, read through it and be sure you know what is needed by the ticket.
Then confirm whether the fix was added as required from our live demo of OpenMRS 1.11 from here .
After confirming the fix, add "1.11-release-tested-pass" to label, otherwise add "1.11-release-tested-fail"
You can also add any comment(s) to the ticket when necessary.
Wishing you the best testing experience
After testing a ticket and you find it good for release, add a label named: 1.11-release-tested-pass
Otherwise if you find issues that need to be addressed, add a comment about your findings and a label named: 1.11-release-tested-fail
To be added after the end of each sprint.