Skip to end of metadata
Go to start of metadata

Form Tab Crash

Tested byCategoryFixedVerified
Reagan MbitiruBugYes24th April, 2013

Description

mUzima crashes after a form has been deleted

Steps to reproduce bug 

  1. Download more than one form
  2. Under Forms --> Downloaded, select any form (not the first)
  3. The delete action bar is displayed at the top
  4. Select any other tab, the delete action bar is still displayed (THIS SHOULD NOT BE THE CASE) - This has been fixed: Reagan Mbitiru 
  5. Click the delete Button (Form Deletes successfully)
  6. Return to downloaded tab
  7. Click any form
  8. The app crashes at this point

Concept crash

Tested byCategoryFixedVerified
Reagan MbitiruBugYes24th April, 2014

Description 

The app crashes when concept definitions are 'quickly' deleted using the Concept settings section of the app.

Steps to reproduce bug 

  1. On the Add Concept Settings Page
  2. When you have several concepts
  3. Click the delete button for the concepts quickly
  4. The app crashes at this point

Addition of functionality to add multiple concepts at once

Tested byCategoryFixedVerified
Reagan MbitiruBugNo24th April, 2014

Description 

Allow multiple concepts to be selected and deleted at the same time

Logout Crash 1

Tested byCategoryFixedVerified
Reagan MbitiruBugYes24th April, 2014

Description 

Steps to reproduce bug

  1. Login to app
  2. Clients --> client --> Forms --> Fill a form
  3. Save draft
  4. On the client summary page
  5. Menu --> Logout
  6. This takes you to the login page
  7. Click the back button
  8. Momentarily you will see the last page you were in
  9. The app crashes at this point

Logout Crash 2

Tested byCategoryFixedVerified
Reagan MbitiruBugYes24th April, 2014

Description 

Steps to reproduce bug 

  1. Login to app
  2. Clients --> client --> Observations
  3. Menu --> Logout (PS: mUzima crashes at this point now)
  4. This takes you to the login page
  5. Click the back button
  6. Momentarily you will see the last page you were in
  7. The app crashes at this point


Logout bug

 

Tested byCategoryFixedVerified
Reagan MbitiruBugNo24th April, 2014

Description 

When a provider logs out, pressing the back button takes you to the last activity you were in, A  user should be required to relogin to gain access to previous activities.

Steps to reproduce bug 

  1. Login to app
  2. Select the "Clients" option
  3. Select details for a specific client
  4. Logout 
  5. Select the back button and the clients details are detailed

Login Crash 1

Tested byCategoryFixedVerified
Reagan MbitiruBugNo24th April, 2014

Description 

Steps to reproduce 

PS: This should be tried out only after a successful login and logout 

  1. On the login page,
  2. Enter a valid username BUT add at the end a space, a comma, a dot (I have tested those)
  3. Enter valid password
  4. Click Login
  5. The app crashes at this point

 

Login Crash 2

 

Tested byCategoryFixedVerified
Reagan MbitiruBugNo24th April, 2014

 

Description 

Steps to reproduce 

  1. Login to the app using a valid set of credentials 
  2. Select the "Clients" option from the dashboard
  3. Select to view details for a specific client
  4. Select a form to fill for the specific client
  5. Go back to the "Observations" section of the app
  6. Select the "Cohorts" option and refresh all cohort data
  7. Logout of the application
  8. A user is unable to login again using a valid set of credentials (IOException thrown)

Forms Page Crash

Tested byCategoryFixedVerified
Reagan MbitiruBugYes24th April, 2014

Description 

Steps to reproduce 

  1. On the Cohorts page
  2. Select All Tab
  3. Select several cohorts and click download
  4. Click back while the download is still on going. This takes you to the dashboard
  5. Select Forms
  6. The app crashes at this point

Synchronizing Form Crash

 

Tested byCategoryFixedVerified
Reagan MbitiruBugYes24th April, 2014

Description 

Steps to reproduce

After pressing the sync button, the application will crash. The form data is sent to the server but it is showing the application stopped working dialog.

Orientation Change anomaly

Tested byCategoryFixedVerified
Reagan MbitiruBugYes24th April, 2014

Description 

Steps to reproduce

  1. Login to the app
  2. On the home page, select forms or cohorts
  3. While on the forms page, change orientation
  4. Click the back button or press the back action item on the bar
  5. Behavior: App logs out and takes you to the login page
  6. Expected: App should take you to the dashboard
  7. The same happens when you change orientation while on the dashboard

PS: Once orientation is changed to landscape, the muzima logo is placed to the left of the login forms. Once app orientation is changed, the muzima logo should appear above the login credentials. This responsive behavior does not occur, the elements remain squeezed in their landscape orientation rather than being realigned when in portait mode

Dispensary form error

Tested byCategoryFixedVerified
Reagan MbitiruBugYes24th April, 2014

Description 

Steps to reproduce

If entering height and weight, BMI is computed.  If scrolling up and changing weight and/or height, it does not change the value for BMI.

Force Re-installation

Tested byCategoryFixedVerified
Reagan MbitiruRuntime bugCould not be replicated24th April, 2014

Description 

Steps to reproduce

Somehow the database gets locked more a times hence giving an exception while saving forms forcing for the re-installation of the application.  This happens mainly when the form throws a validation error on a field while saving as complete.   http://pastebin.com/R5M5Zhac

Losing skip logic 

Tested byFixedVerified
Reagan MbitiruYes24th April, 2014

Description 

Steps to reproduce

Saving the form as draft seems to lose the skip logics when reopened

Incorrect behavior on repeated table 

Tested byFixedVerified
Reagan MbitiruYes24th April, 2014

Description 

Steps to reproduce

When inserting a new row for the repeated table, it will grab the value from previous row and put as default for the new row.  Correct behavior is that the values for new row should be null.

Server URL should not be shown on subsequent login(s)

Tested byFixedVerifiedNotes
 Reagan Mbitiru Yes 24th April, 2014Bug occurs on seemingly random logins (after timeout periods have expired)

Description 

Steps to reproduce

On subsequent login(s) the input field for the the server url is still is still displayed.

Cannot view data in form draft

Tested byCategoryFixedVerified
Reagan MbitiruRecommendationNot Implemented24th April, 2014

Description 

Steps to reproduce

Saving the form as draft works okay but we cannot view the data filled from the observations tab,

Losing data from form draft 

Tested byFixedVerified
Reagan MbitiruNo24th April, 2014

Description 
If a provider fills the CDM dispensary form on the section for "Your current other medications" then save the form as draft, reopening this form will have lost the collected data

Steps to reproduce 
1. Open the CDM dispensary form (HTML version) 
2. In the Encounter details section, once a user selects either "Second Dispensary Visit" or "Return Dispensary visit" or "Referred from Clinic", the pHCT review section is hidden.
3. The form is saved as a draft.
4. Once the form is selected from the Incomplete tab, the pHCT review section is displayed yet it should remain hidden. 

Steps to reproduce bug 2
1. Open the CDM dispensary form (HTML version) 
2. Select any drug from the "Your current medications" or the "Medications prescribed" or "Referrals ordered" sections
3. save the form as draft.cohorrt
4. Go to the incomplete tab on the patient forms and reopen the form
5. The data collected in the "Your current medications" sections is goned

Reason for missing drug does not respond

Tested byFixedVerified
   

Description 

Steps to reproduce

Unable to  have subsequent login in offline mode

Tested byCategoryFixedVerified
Reagan MbitiruBugYes24th April, 2014

Description 

Steps to reproduce

The application should allow users to do the subsequent login(s) when they are offline currently we can only login when at least the device has a network connection and not necessarily connecting to the server.

Numeric text pad for numeric fields

Tested byFixedVerified
Reagan MbitiruYes (especially on fields capturing dosage information)24th April, 2014

Description 

Steps to reproduce

When the fields are numeric, it should change to numeric text pad.

Input fields hidden by virtual keyboard when logging in

Tested byCategoryFixedVerified
Reagan MbitiruUsability FeatureNot Fixed24th April, 2014

Description 

Steps to reproduce

When logging in, the soft keyboard displayed covers the entry input fields and a user has to use the back button to dismiss the soft keyboard before entering the login credentials. Recommendation is to use the activity adjustSize property or a ScrollView to ensure that the input fields are always displayed

 

Cohort prefix does not restrict the cohorts to be downloaded

Tested byCategoryFixedVerified
Reagan MbitiruBugNot Fixed24th April, 2014

 

Description 
Adding cohort prefix does not restrict the cohorts to be downloaded

Steps to reproduce 
1. Go to  the settings page 
2. Select the add cohort prefix option
3. Add a cohort prefix to restrict download
4. Go the cohorts section and here you can view and download all cohorts regardless of the restrictions .

mUzima does not preserve state when use of the app is interrupted

 

Tested byCategoryFixedVerified
Reagan MbitiruBugNot Fixed24th April, 2014

 

Steps to reproduce

  1. Select to fill a form for a particular client
  2. Navigate to the home screen of your android application
  3. Select the mUzima launcher
  4. mUzima loads the dashboard rather than to the form that a user was filling 

 

Observations not downloaded when large cohort data is downloaded to mUzima

Tested byCategoryFixedVerified
Reagan MbitiruBugNot Fixed24th April, 2014

 

Description 

 

When a lot of cohort data is downloaded onto mUzima, observations data is not included as part of the download

 

Steps to reproduce 
1. Select the "Cohorts" option from the dashboard
2. Select a cohort with a large number of clients (>300) and download cohort data
3. Go back to Observations section for client and no observations will have been recorded


  • No labels