Summary

Use separate test scenario and workload files for all test runners in Astrolabe.

Currently the Atlas and Kubernetes tests use different test formats. The Atlas tests put the test scenario and workload in the same file, but the Kubernetes tests put the test scenario and workload in separate files. Keeping them in separate files can make implementing tests and test runners easier. It also means the workload file format conforms exactly to the Unified Spec Test format.

This is a follow-up task to drivers-atlas-testing PR 141.

Motivation

Who is the affected end user?

Astrolabe developers.

How does this affect the end user?

Currently the Atlas and Kubernetes tests use different test formats. The Atlas tests put the test scenario and workload in the same file, but the Kubernetes tests put the test scenario and workload in separate files. The difference is confusing.

How likely is it that this problem or use case will occur?

Only comes up when adding or modifying tests or test runners. Is relevant now becuase of the Continuous Containerized Testing work.

If the problem does occur, what are the consequences and how severe are they?

Confusion.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

No.