[go: up one dir, main page]

Alcotezt UX improvements

The Alcotezt project has incurred some usability regressions on unit test execution.

Problems

Notably, it is no longer possible, or hard to:

  • (A) Select all tests in a specific folder / package / file
  • (B) Selecting sub-tests: we now group tests at a coarser-grain, which makes it harder to selected individual cases.
    • In alcotest, a "test suite" is a sequence of "tests" that are composed of a sequence of "test cases".
    • In tezt, there is only "tests" that are loosely grouped by "files" and horizontally by "tags".
    • With alcotezt, we group each alcotest "test" into a tezt "test". consequently, we can no longer execute individual test cases.
  • (C) Invocation headers
  • (D) Understanding where a failing test in the CI is located
  • (E) Having both runtest and runtezt is confusing

Constraints on solution

  • opam tests must continue to work
  • runtest/runtezt should work
  • tezt entrypoint should work
  • tezt --list should give legible output

Proposed solutions

Edited by lykimquyen