GSoC 2022: Improving 3.x E2E Tests - Project Updates

Community GSoC
, ,
#1

Hi all! I will be working on the project ‘Improving 3.x E2E Tests’ for Gsoc 2022. The project will produce a reliable and deterministic end-to-end test framework for the 3.x. This thread will be used to update the community about the project’s progress.

For more details - GSoC 2022: Improving 3.x E2E Tests - Projects - OpenMRS Wiki

Project proposal - GSoC 2022: Improving OpenMRS 3.x E2E Testing Framework (latest) - Google Docs

Epic link - [O3-1313] Improving 3.x E2E Tests. - OpenMRS Issues

Primary mentor - @jayasanka Backup mentor - @bistenes

1 Like
QA for O3 + OHRI: Summary of main current qa initiatives
Improving E2E Automated Tests for the OpenMRS 3.0 RefApp - Final Evaluation
#2

great work @pasindur2 hope you follow up with @ibacher. He might have an idea on how to raise the visibility of 3.X tests

You might also find OpenMRS 3.x Requirements Rubric (QA Spreadsheet) an interesting resource too.

cc @zacbutko

1 Like
#3

Thank you @jnsereko for the suggestions.

Project Update -

Milestone definition for the project - Milestones for the Project of Improving 3.X E2E testing Gsoc 2022 - Google Docs

#4

Update- Created a PR to change the configuration and update the readme guidance to the local instance test backend for 3.x E2E testing. link

cc: @jayasanka @bistenes @qateam

#5

Project update to 2022-07-01T18:30:00Z

  1. Created a pr to bring refapp 3 E2E test to the new repository (Login test) and set up a Ci pipeline to integrate the test results -

pr -

New repository - GitHub - openmrs/openmrs-test-3refapp

  1. Created pr to remove 3.X stuff from GitHub - openmrs/openmrs-contrib-qaframework repo.

PR -

CC: @jayasanka @bistenes

#6

Project updates to 2022-07-20T18:30:00Z

  1. Worked on fixing the data mutation issue.

Jira ticket -
https://issues.openmrs.org/browse/O3-1316

Pull request -

Had a few issues with;

  • Setting up the back end - Got fixed (Talk discussion)
  • Errors with MySQL connection for making a dump of the database; the connection issue got fixed by mysqldump -h localhost -P 3306 --protocol=tcp -u openmrs -popenmrs openmrs > openmrs.sql command. And it worked after setting the database port to 3036 in docker. So I could be able to make a dump of the database. But dumping data for tables is stopped at the first execution. Error log - mysqldump error log - Pastebin.com Slack thread - Slack
  1. Worked on fixing two existing tests.
  • Patient registration test.

Jira ticket -
https://issues.openmrs.org/browse/O3-1403

Pull request -

The test checks have passed. And the pull request is ready for review and merge.

Jira ticket -
https://issues.openmrs.org/browse/O3-1406

Pull request -

The test checks have passed. And the pull request is ready for review and merge.

cc: @jayasanka @ibacher @bistenes

1 Like
#7

By defining column statics the dump works fine.

Command - mysqldump --column-statistics=0 -h localhost -P 3306 --protocol=tcp -u openmrs -popenmrs openmrs > openmrs.sql

Both commands for dumping the database and restoring work fine. The pr O3-1316: Implement a feature in 3.x E2E testing tool to avoid data mutations in tests by pasindur99 · Pull Request #3 · openmrs/openmrs-test-3refapp · GitHub is also ready for review.