Child pages
  • 2015-04-23 Developers Forum
Skip to end of metadata
Go to start of metadata

How to Join

 Click here to expand...

 

In person

Courtesy, please

If you are joining remotely via telephone, Adobe Connect, or Skype, please use a headset-microphone, or at least earphones. Please use the mute feature when you are not speaking.

Interactive meeting - Adobe Connect

  • We routinely share a screen during the call. You can view the screen via our Adobe Connect meeting room at http://connect.iu.edu/omrsdf. For large meetings, the room has the ability to broadcast audio and connect to a telephone-based system as well, as controlled by the meeting hosts.

By telephone

  • US telephone number: +1-888-510-4073
  • Access code: 24222#

By Browser

Chat/IRC

  • Chat is available in the Adobe Connect meeting room (see above).
  • A backchannel meta-discussion during the meeting also occurs on IRC.

 

Agenda

  • Quickly review previous meeting minutes (5 min)
  • Review next meeting agenda

Minutes

View at notes.openmrs.org

 

OpenMRS Developers Forum 2015-04-23
Recording: http://goo.gl/Sz2ILH (Audio) 
Attendees
  • Burke Mamlin
  • Michael Downey
  • Tim Nicholson
  • Rafal Korytkowski
  • Tharunya _
  • Tomasz Mueller
  • Darius Jazayeri
  • Willa Mhawila
  • Saptarshi Purkayastha
  • Ada 
  • Daniel Kayiwa
  • Manika Praveenkumar Maheshwari
  • Ryan Yates
  • Maurya
  • Karl Wurst
Agenda & Notes
  • Review last week TODOs
  • TODO: Burke to notify presenters about their dev forum topics
  • TODO: Someone to Set up CI builds for MariaDB, PostgreSQL, and SQLServer, Oracle (We assume these will not be green lights)
  • TODO: Someone to Create tickets to address problems that occur for alternate DBs
  • TODO: Someone to Schedule sprint(s) to address DB tickets
  • QA Systems (load testing and performance testing)
  • Follow up from the last wave of this topic: IU no longer allows non-IU systems to use NeoLoad & Dynatrace. :-(
  • Functional Testing
  • JBehave
  • Need to be "smart" about functional testing, since these can be brittle, so need to focus on high value tests and create them in a way that is as robust as possible
  • We have incoming volunteers who aren't devs but are interested & willing to do manual functional testing ... unfortunately we don't usually have much for them to do
  • Acceptance Testing
  • Performance Testing
  • OpenMRS 1.8 focused on performance improvements and, for that relese, we set up a CI build onto a spare server (non-VM) to generate a report of performance metrics (e.g., patient search, dashboard load time, etc.).
  • Is this a priority for us?  Would we like to have build tests that check performance?  Break builds if performance metric doesn't meet goal?
  • Implementations notice quickly with patient search takes 2 minutes, but we may not need a fancy, automated system to address these issues (in terms of priorities)
  • There are likely higher priorities – e.g., functional testing, testing against other databases, testing deployments (large db, upgrades, etc.)
  • What did Soldevelo and the Mifos team establish for their app? Sequence: Functional Testing, (Automated) Acceptance Testing, Performance Testing, Release Testing
  • Load Testing
  • How many concurrent users does OpenMRS support (on specific server specs)?
  • Darius: Lower in the priority list
  • Corollary: How many concurrent users do most large implementations have, and what type of work are those users doing? 
  • Unit Testing
  • We feel like we're doing reasonably well
  • Should probably do more mocks, so testing is more reliable & runs faster
  • How long should it take to run unit tests?  How long is "too long" (when devs stop using skipTests by default)?
  • "If you have tests that are useful, but take longer than you want the commit suite to run, then you should build a DeploymentPipeline and put the slower tests in a later stage of the pipeline." - Martin Fowler http://martinfowler.com/bliki/UnitTest.html
  • Expect devs to run their tests using IDE as they develop.
  • Expect devs to run full suite of tests before committing code.
  • TODO: push for mocks over integration tests
  • TODO: document how to test within IDE in dev pages in wiki
  • Infrastructure update
  • OpenMRS Talk & Google Groups
  • Migrations away from Google Groups: Implementers Group on 2015-03-05, Developers Group on 2015-04-10
  • Increased activity: Nearly 20% of all Talk topics (159) and posts (817), and 30% (23,684) of all emails since early 2014, happened in the last 30 days
  • Last month: 1,224 unique visitors (up 6%) spent 7m40s (up 11%) during a typical visit
  • 570 users and counting have signed in with their OpenMRS ID & participated
  • Confluence wiki updates
  • Now running 5.7.3
  • Some performance improvements, but required doubling available memory to upgrade
  • New fonts, styles, colors, etc.
  • Improvements to authentication systems
  • Anticipated OpenMRS ID Dashboard 2.1 GSoC project. Highlights:
  • Support two-factor authentication for OAuth-based sign ins
  • Automatic synchronization (creation) of all OpenMRS ID users in Talk/Discourse
  • Build a REST API for working with user profile data
  • 3rd-party sign in and profile creation from Google, Facebook, GitHub, etc.
  • Various backend improvements
  • Private authentication network for improved Atlassian performance (direct LDAP auth to eliminate dependency on bad Crowd sync code)
  • After Action Review
  • What did you expect to happen?
  • What actually happened?
  • What can we do better?
  • Preview Next Week
  • 30 April: OpenERP showcase w/ Bahmni, OpenMRS 2.2 retrospective
  • 7 May: Google-MSF Ebola project

TODOs

Outstanding TODOs  (${entries.size()} issues)

Summary Assignee Created Due
Loading...
Refresh

Create a TODO: http://go.openmrs.org/todo

Transcripts

  • Audio recording of the call: Listen online or download (available after the meeting)

 

 

  • No labels