Ozone E2E Test Suite

Welcome to Ozone automated test suite.

• Setup Steps
  • Step 1. Setup the project
  • Step 2. Run Ozone e2e tests
• Configurations
• Project Structure
• Guide for writing tests
• GitHub Actions integration

(Table of contents generated with markdown-toc)

Setup Steps

Step 1. Setup the project

Clone the project

git clone https://github.com/ozone-his/ozone-e2e

Navigate into the project

cd ozone-e2e

Install dependencies

yarn install

Step 2. Run Ozone e2e tests

npx playwright test

Configurations

This is underdevelopement/WIP. At the moment, there exists a git-shared .env file used for configuring environment variables.

By default, the test suite will run against Ozone dev server. You can override it by changing the environment variables beforehand:

# Ex: Set the server URL here
export E2E_BASE_URL=https://ozone-dev.mekomsolutions.net

Project Structure

The project uses the Playwright test runner and, generally, follows a very simple project structure:

e2e
|__ tests
|   ^ Contains test cases
|__ utils
|   ^ Contains utilities needed to setup and tear down 
|     tests as well as methods required by the tests to run

Guide for writing tests

When writing a new test case, create a new spec in ./e2e/tests

GitHub Actions integration

The pro.yml workflow is split into two jobs, one that runs upon Git pull requests, and Git push(es). The other runs tests on an environment specified during runtime. The difference between the two is that, the later is run manually via GitHub Actions. Note: When manually running the tests, you need to choose the test environment at runtime.

The foss.yml workflow contains one job that runs Ozone FOSS specific tests. Note: You need to provide O3, Odoo and SENAITE base URLs at runtime.