tests

Running the tests

Unit tests

Before we start the application, let's try running the tests. Create the test databases:

$ MIX_ENV=test mix do ecto.create, ecto.migrate

# Or if you are using specific database URLs:
$ MIX_ENV=test DATABASE_URL=postgres://localhost/ewallet_test_db LOCAL_LEDGER_DATABASE_URL=postgres://localhost/local_ledger_test_db mix do ecto.create, ecto.migrate

Then, let's run the tests:

$ mix test

# Or if you are using specific database URLs:
$ DATABASE_URL=postgres://localhost/ewallet_test_db LOCAL_LEDGER_DATABASE_URL=postgres://localhost/local_ledger_test_db mix test

You should see the results similar to below:

==> local_ledger_db
Finished in 0.5 seconds
57 tests, 0 failures

==> ewallet_db
Finished in 2.3 seconds
249 tests, 0 failures

==> local_ledger
Finished in 0.9 seconds
24 tests, 0 failures

==> ewallet
Finished in 3.4 seconds
141 tests, 0 failures

==> admin_api
Finished in 4.4 seconds
184 tests, 0 failures

==> ewallet_api
Finished in 4.5 seconds
134 tests, 0 failures

All the tests should pass. If some tests are failing, double-check you have install all the dependencies. If you keep getting the failures, you can get in touch with us on Gitter!

Acceptance tests

We offer acceptance tests at omisego/e2e written using Robot Framework. These tests rely on initial seeded data which are 2 admins and a base account.

Prior to running the acceptance tests, you will need generate the sample data needed for the tests:

$ E2E_ENABLED=true mix seed --test --yes

--yes option allows to skip all prompted confirmations which is ideal when ran on an automation server.

You will need to add a few environment variables before running the seed, check Environment Variables for more information.

Load tests

A minimal load test suite is available in the load_tester sub-application.

To run the load test, first seed the data into your target eWallet server with the command below. Note that this command uses the same seed as the acceptance tests, with the exception that it sets a custom admin email and password to be used by the load test suite.

$ E2E_ENABLED=true \
  [email protected] \
  E2E_TEST_ADMIN_PASSWORD=loadtesting \
  mix seed --test --yes \

Once the target server is seeded, run the load test suite from a different machine with the following command:

$ cd apps/load_tester && \
  LOADTEST_TOTAL_REQUESTS=600 \
  LOADTEST_DURATION_SECONDS=60 \
  LOADTEST_PROTOCOL=https \
  LOADTEST_HOST=your-server-hostname \
  [email protected] \
  LOADTEST_PASSWORD=loadtesting \
  mix run -e 'Chaperon.run_load_test(LoadTester.Runner, output: "load_test_result")'

With the command above, the load test suite will generate 600 / 60 = 10 requests per second. You may adjust this rate by changing the LOADTEST_TOTAL_REQUESTS and LOADTEST_DURATION_SECONDS environment variables.

The result is saved to /apps/load_tester/load_test_result.csv.