pasindur2
(Pasindu Rupasinghe)
June 19, 2022, 12:39pm
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
jnsereko
(Joshua Nsereko)
June 19, 2022, 12:58pm
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
pasindur2
(Pasindu Rupasinghe)
June 19, 2022, 1:09pm
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
pasindur2
(Pasindu Rupasinghe)
June 21, 2022, 1:08pm
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
pasindur2
(Pasindu Rupasinghe)
July 2, 2022, 6:27am
5
Project update to 2022-07-01T18:30:00Z
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 -
openmrs:main
← pasindur99:O3-1375
opened 02:58AM - 29 Jun 22 UTC
## Purpose
The pull request is created to bring RefApp 3.X test to a new reposi… tory and this pull request is related to the issue ticket number [O3-1375](https://issues.openmrs.org/browse/O3-1375) [O3-1360](https://issues.openmrs.org/browse/O3-1360)
## Goals
- The goal of this pr is to bring the 3.x E2E automated test framework into a new place.
## Approach
- Restore the 3.x E2E testing framework.
New repository - GitHub - openmrs/openmrs-test-3refapp
Created pr to remove 3.X stuff from GitHub - openmrs/openmrs-contrib-qaframework repo.
PR -
openmrs:master
← pasindur99:O3-1375
opened 04:23AM - 30 Jun 22 UTC
## Purpose
* The purpose of this pull request is to remove the 3.x related s… tuff from this repository since the 3.X test will bring to a new repository. [New Repo](https://github.com/openmrs/openmrs-test-3refapp)
* Issue ticket number - [O3-1375](https://issues.openmrs.org/browse/O3-1375)
CC: @jayasanka @bistenes
pasindur2
(Pasindu Rupasinghe)
July 21, 2022, 3:59pm
6
Project updates to 2022-07-20T18:30:00Z
Worked on fixing the data mutation issue.
Jira ticket -
https://issues.openmrs.org/browse/O3-1316
Pull request -
openmrs:main
← pasindur99:O3-1376
opened 07:37PM - 10 Jul 22 UTC
## Purpose
The pull request is created to implement a feature in 3.x E2E testin… g tool to avoid data mutations in tests. And this pull request is related to the issue ticket number [O3-1316](https://issues.openmrs.org/browse/O3-1316)
## Goals.
- This pr aim is to avoid the data mutation issues related to some tests in 3.X E2E testing tool.
## Approach
- Create Script files for the following purposes.
1. Take a Dump File of a database.
2. Restore the database.
- Create npm commands to run the following scripts.
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
Worked on fixing two existing tests.
Patient registration test.
Jira ticket -
https://issues.openmrs.org/browse/O3-1403
Pull request -
openmrs:main
← pasindur99:O3-1402
opened 05:35AM - 19 Jul 22 UTC
## Purpose
The pull request is created to fix the existing patient registration… E2E test. And this pull request is related to the issue ticket number [O3-1403](https://issues.openmrs.org/browse/O3-1403)
## Goals.
- This pr is to place the existing patient registration test in 3.X test framework.
## Approach
- Create a feature file and a step definition file for the patient registration test.
- Creat GitHub workflow.
- Migrate the test result to the dashboard.
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 -
openmrs:main
← jnsereko:O3-1406
opened 02:48AM - 11 Jul 22 UTC
As all seam to be working, i got a thing with verifying that there is no duplica… tion in returning of results.
By this i mean that the names might be the same but the uuid is always different.
Anchor's href is always different (unique) however much the patient names might be the same.
How can we use the anchor to verify that there is no duplication in results
### Issue Link -> https://issues.openmrs.org/browse/O3-1406
cc @dkayiwa @jayasanka-sack @pasindur99 @ibacher
The test checks have passed. And the pull request is ready for review and merge.
cc: @jayasanka @ibacher @bistenes
1 Like
pasindur2
(Pasindu Rupasinghe)
July 22, 2022, 3:39am
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.