Skip to content
Select theme

Running the e2e distributions

Two e2e runners, three target environments, six distributions. Both runners are measured against the same docker compose stack, so a difference in result is a difference between the suites and nothing else. Pick the one you mean to run.

Go runner (the default, one binary per environment)

Mocked stack e2e-fega

Nine stages against the local compose stack. What CI runs on every push, and what ./dev.sh start gives you with no setup at all.

Live staging e2e-egadev

Six stages against egadev.uio.no. Runs on a host as well as in the container, and needs real credentials and key paths.

Not implemented e2e-gdi

A placeholder that exits 1 on purpose, so a GDI run can never be mistaken for a pass.

JUnit runner (retiring, one test class per environment)

Mocked stack FEGA

The same nine checks as e2e-fega. The only distribution you can run from an IDE, which makes it the one to reach for when debugging a service.

Retiring · #851
Live staging EGA_DEV

The same six checks as e2e-egadev, against the same live environment.

Retiring · #851
Empty GDI

Seven test methods with empty bodies. It asserts nothing and always passes, which is worse than the Go placeholder that fails.

Retiring · #851

Built from f91944d