Tuesday, February 8, 2011

More Bugs, More Problems.



For openMRS, joining the bug tracker was very simple and straight forward. Searching through the bug logs was quite simple too, I was able to find the oldest open bug relatively easily it took time to derive the way the bugs were divided though. Bugs are given 3 different typings,Could, Should, and Must. The oldest bug under the could category is trunk-333.The oldest "should" bug is trunk-330. Both bugs have a severity level 3 so they are not a the top of the list of things to do but one team are looking into fixing trunk-333 and as of now trunk-330 is not assigned to anyone.

Reproducing a bug
After searching through the bugs  I found trunk-1702 .The problem was that ConceptService#saveConceptNameTag() does not save changes to the object rather it returns an existing object from the database. There is no other method to update ConceptNameTag either. My assignment was to see if I could reproduce the bug in the current build, OpenMRS 1.8. Despite my best efforts I was not able to reproduce the bug no matter how I tried, this bug has been fixed since version 1.6 so the original fix still does hold. I emailed Rafal Korytkowski to see if there are any steps that could be taken to reproduce the bug, he is pretty active so he should get back to me sometime soon.

Bug Triaging
For bug Triaging I chose 5 different bugs...

1. Trunk-1975-The BinaryDataHandler "getObs" method creates a complex obs where the data component is a FileInputStream. The getObs method leaves this input stream open when it returns the obs so that other methods (such as the ComplexObsServlet) can access the stream.
However, if the stream is not explicitly closed, the lock on the file is never released until the webapp is restarted. 
This ticket needs a severity level of 4 becauses if this project is going to be use by people who are not computer savvy, then they may/will not know how to explicitly close the stream. This ticket is well documented.
2. Trunk-1955 With this bug if you start to type Miriam and then back space it and type James Arbaugh, it yields results for "Mi". While this is bad, the severity level of this a lot lower than the first bug but it is necessary to fix. It is written well a  and definitely needs to be addressed.
3. Trunk-1963  this bug is a bit more confusing for me, maybe because I am new to OpenMRS or its the way its written. The original poster should probably reword this issue so that the severity level can be determined.
4. Trunk-201 this is an ideal bug report. The user provides not only what the bug does, the user tell you the exact steps used to reproduce this bug which will be very helpful when others try to fix it. The severity level should probably be about 3.
5.Trunk-2003 This bug is interesting because when a user adds a new patient address or name or identifier and they get sent back to the form after validation errors. The steps to reproduce it are very simple and its severity level is moderately high.

No comments:

Post a Comment