Skip to content

Investigate better ways to Test our UI #1515

Open
@Al12rs

Description

@Al12rs

Spike

Proposal

We currently have stopped writing tests for UI as we don't really have a good system for them.
It isn't clear exactly what should be tested, only parts of VMs, all VMs, more than that?

Tests should be easy and quick to write, should be reliable and should have no issues when executed in parallel.

We should also define what kind of test approach want to support, regression testing, TDD, unit tests?

Impact

Currently ui tests are a pain to write, can't be run in parallel, are unreliable, break easily and have a higher maintenance cost than regression prevention value.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Epic: Tech-debtTechnical debt, this needs solving in the long-termSpikeAn investigation taskTech: Tests

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions