You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we are connected to the dev backend, create a new user in the platform and update the fixture and use that ID for this test
Create a new file called patient_locationt.cy.ts and related object file
Things to be Covered
Create a new multi-type location (Room, Bed, and House) and verify that the location search functions correctly. (Test-1)
Create a new bed location, navigate to the encounter page, open any live encounter, and confirm that you can assign the patient to the new location in the "Manage Location" section. (Test-2)
The text was updated successfully, but these errors were encountered:
@nihal467 This looks like an interesting E2E issue, but I have a few queries regarding location creation and updates to ensure the test covers necessary scenarios:
In Test-1, should it create all three location types (Room, Bed, House) within a single test, or would it be better to have separate tests for each type to ensure more granular validation?
In Test-2, What should happen if the assigned location is already occupied? Should it include error handling scenarios in the test?
Looking for the insights
Since there are only three location types, we should keep them in a single test rather than separating them. Splitting them would add unnecessary steps and increase execution time without any additional benefit.
Currently, if a location is already occupied, it does not appear in the dropdown. Since we're connected to the local development backend, this could lead to flaky tests. To avoid this, we should ignore the occupied locations for now.
Alright i see ,thanks for the clarification . Well i know it's an extensive issue to work on but i would like to have my hands on this issue ,Thus if you consider me assigning me this issue i will surely try and make the things work within a few days .
Describe the Test
Create a new cypress test to add a new location in a facility and cover all its happy flow functionality
Rules to be followed
docs.ohc.network/docs/care/development/guidelines-to-write-cypress
Things to be Covered
The text was updated successfully, but these errors were encountered: