Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OZ-588: Documented running E2E tests locally. #13

Merged
merged 2 commits into from
Jun 18, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions docs/devs/e2e-tests.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,33 @@ All configuration variables are set to the desired values by editing and saving

Additionally, the `.env` file contains a range of configuration variables that specify the URLs for accessing the various HIS components in each test environment, as well as the credentials needed to execute the test cases.

### Running tests against a local instance

When developing on Ozone, you will likely run a local instance of the HIS and want to execute the E2E tests against it. To do this, update the URL coordinates for the **dev** environment profile in the `.env` file.

Typically, you may set the URLs in your local version of the `.env` file like this:

```bash
# OpenMRS
O3_URL_DEV=http:https://localhost
O3_URL_QA=
O3_URL_DEMO=

# ...

# Odoo
ODOO_URL_DEV=http:https://localhost:8069
ODOO_URL_QA=
ODOO_URL_DEMO=

# SENAITE
SENAITE_URL_DEV=http:https://localhost:8081/senaite
SENAITE_URL_QA=
SENAITE_URL_DEMO=
# ...
```
Continue this pattern for all components running locally by identifying their local URL in your development environment, and edit the `.env` file accordingly.

## Running Tests

### Default test execution
Expand Down