(chore) O3-3574 : Refactor E2E test for appointments #1287
Conversation
| test('Add an appointment', async ({ page, api }) => { | ||
| const appointmentsPage = new AppointmentsPage(page); | ||
| test.describe.serial('Running appointment tests sequentially', () => { | ||
| test('Add an appointment', async ({ page }) => { |
There was a problem hiding this comment.
@jayasanka-sack @kdaud I would like to seek your views concerning the use of test.describe in scenario of sequential operations e.g. create, edit and delete like this one.
This is to improve some of our e2e tests going forward and prepare towards writing more advanced test cases.
There was a problem hiding this comment.
@chimanwadike the refactor should involve decoupling the test scenarios for adding, editing, and canceling an appointment.
@kdaud this is noted. |
@kdaud I've been away for a while now. Following your last comment, it appears we would have to create separate appointments to test edit and cancel if these test cases must be decoupled that far. In order to decouple the tests the way you've explained and how I understand it, we could run into overheads of more API calls and could lead to slower tests in the grand scheme which is neither what we need. I'm thinking there maybe no need for this PR, what do you think? |
Requirements
Summary
This PR refactors existing e2e tests for appointments by writing separate tests for adding, updating, and canceling.
This is to increase test clarity and visibility.
Related Issue
https://issues.openmrs.org/browse/O3-3574