OpenMRS sample bug: Difference between revisions

imported>Chrishay7
(Created page with "= OpenMRS bug walkthrough = Talk to Chris Hay and Katherine Ye. Check out code from here: https://github.com/hypotext/openmrs-core We'll be walking you through fixing [http...")
 
 
(2 intermediate revisions by 2 users not shown)
Line 1:
= OpenMRS bug walkthrough =
 
Talk to Chris Hay and Katherine Ye if you have any questions.
 
Check outThe code frombeing used for this bug walkthrough can be found here: https://github.com/hypotext/openmrs-core
 
We'll be walking you through fixing [https://issues.openmrs.org/browse/TRUNK-3780 this bug], testing changes in the webapp, writing tests, and submitting a pull request!
Line 14:
 
== Analyzing a Ticket ==
After clicking on one of the links above, you'll come to a page that lists the details for an issue/feature that needs work. Ideally, it'll provide descriptions of the current behavior, the desired behavior, and areas of interest that might help fix the issue. Make sure to read through the comments section to get a feel for the progress that's already been made.
 
 
Line 22:
 
== Replicate the Issue ==
After familiarizing yourself with the ticket, you then need to replicate the error. This will help provide additional context/error logs about the issue and will also ensure that you will be able to test whatever changes you make. To do this, you'll likely need to start the webapp. Help in doing that can be found [https://github.com/hypotext/OpenMRS-dev-setup/wiki/Running-the-OpenMRS-webapp-and-viewing-changes-in-code here] (if using the VM setup, the webapp should already be running).
 
Sample ticket: Start the server and go to the webapp. Login using admin/Admin123 (try admin/test if that doesn't work). Navigate to the patient search and try searching for the names described in the ticket. Can you reproduce the bug? You may need to make some test data in the webapp.
Line 50:
 
== Submitting the Pull Request ==
First, compare your solution to what other students have done. Also take a look at the existing pull requests that might touch the same areas of code, and make sure they don't clash (optional).
 
Ask Chris or Katherine to help you submit your changes.
Anonymous user