Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
Child pages
  • Testing OpenMRS Platform 1.11 Release Tickets Sprint 2 - 2014
Skip to end of metadata
Go to start of metadata

General Sprint Information: 

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

  • Password: Admin123

Tickets to be tested: 1.11 Release tickets on target for testing

Source Code: https://github.com/openmrs/openmrs-core/tree/1.11.x

Feedback: https://notes.openmrs.org/OpenMRS-Platform-1.11-Release-Feedback

Sprint Start Date: Thursday, 14/08/2014 19:00 UTC (Second Iteration)
Sprint End Date:  Thursday 28/08/2014 19:00 UTC (Second Iteration)

Sprint Goals: 

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:

 

1. Our first/best noticed participant in testing; receives priority ranking in their "OpenMRS contribution" score for their scholarship, or will be able to delegate the same "award" to another scholarship applicant.
2. The second participant; receives a custom OpenMRS shirt.

3. Lastly; listing all the testers/contributors in the 1.11 release notes.

Participants

How to Participate 

  • 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"

  • For tickets that do not require any user interface testing, if you are a developer, take a quick glance at the commits and if they look good, just add the 1.11-release-tested-pass label and comment that you have reviewed. If the commits need some more work, add the 1.11-release-tested-fail label and comment accordingly.
  • You can also add any comment(s) to the ticket when necessary.

  • Feel free to do any other random testing for features which may not have tickets. Include your findings in the feedback notes page above.
  • Wishing you the best testing experience

During Project Notes for the sprint: 

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

Sprint Retrospective:  

To be added after the end of each sprint. 

See Also

  •  

 

  • No labels