cockroachdb / cockroachdb/cockroach

ui: improve UI tests execution in dev environment

Open
#106,581 1 comment 0 reactions 0 assignees View on GitHub
A-cluster-observability C-enhancement O-community T-observability
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

**Is your feature request related to a problem? Please describe.**
Currently, running tests locally is challenging in a way that it only possible to run all tests
for both `db-console` and `cluster-ui` with `dev ui test` command that take long time
to run all tests and doesn't provide easy to read test results (and investigate cause of
test failure).

Running `dev ui test --watch` doesn't provide a way to watch changes for single test
(ie changing single test logic, not function under test, will trigger to re-run multiple unrelated tests).

**Describe the solution you'd like**
extend `dev ui test` command with
- `--filter` to run specific test only
- add parameter to format test results in a way to easy analyse and check test failures
- add `--verbose` param to show/hide warning and debug messages that might spam output logs.
- add option to run tests either for `db-console` or `cluster-ui` only.

Jira issue: CRDB-29629

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.