Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Quick Links

Where to Go: 

Auibutton
iconconfigure
titleQA GitHub Repo (Dashboard and Work Hub)
typeprimary
urlhttps://github.com/openmrs/openmrs-contrib-qaframework
targettrue
  
Auibutton
custom-iconbacklog
iconcustom
titleQA Jira Board (Find/log tickets here)
typeprimary
urlhttps://om.rs/qaboard
targettrue

Guidance: 

Auibutton
iconinfo
titleE2E Frontend Test Steps
typeprimary
urlhttps://openmrs.atlassian.net/wiki/display/docs/QA+Framework+Overview%3A+Steps+to+Take+when+writing+a+Frontend+Test
targettrue
  
Auibutton
iconhelp
titleDetailed E2E Test Dev Guide
typeprimary
urlhttps://openmrs.atlassian.net/wiki/pages/viewpage.action?pageId=22570765
targettrue

QA Support Team meeting details & notes at om.rs/qanotes

Our E2E Test Process


We apply a Workflow-based Approach to E2E tests. This allows us to have happy-path smoke tests grouped by workflows, which test from a user’s perspective. These  We do this because:

  • It's easier to confidently release regularly if your business stakeholders have confidence in a few, not too many, E2E tests that cover happy-path user stories (where things go right). 
  • We don't want to automate every possible click or every possible path - this causes a lot of overhead in maintenance and cognitive burden when reviewing test reports. However, detailed functional tests should still be written for specific features. (Functional tests are outside of the scope of E2E Workflow tests.)


Diagram of the steps to take when creating a frontend test: 

Image Added


Video: Overview of the New QA Framework

Widget Connector
urlhttps://www.youtube.com/watch?v=VrlaFczVjUc&list=PL5jj7JoBifSlygPuQGWF1Nd_zM8m6oD1p

More Documentation & Dev Guides

Child pages (Children Display)