which problems it solve:
Having results normally in jenkins we don't visualize them. The results ( and failed tests) are more volatile and the knowledge of the tests failure is something that rely on some internal knowledge and periods.
For improving our test-suites would be nice to track over like 6 months which tests are most failing, etc.
This can be applied for SUSE-Manager team or all team that support junit in jenkins ( this is for the moment the first format of tests)
More then this i would like to use kubeojo for salt-toaster (https://github.com/openSUSE/salt-toaster)
In cucumber we could track the count of failure of feature (group) and also the steps failed( subgroup).
In this way we can have a nice chart. The same reasoning can be applied also for rspec and other tools that use junit format where tests can be ordered in groups.
We could maybe extend functionality over junit but i think is ok to start with junit
Looking for mad skills in:
This project is part of:
Hack Week 17
open-sTeam is a platform for cooperative work a...
"salt-toaster" allows you to test multiple Salt...
Hackweek 17 Update
During Hackweek 17 I di...
Right now our concourse instance http://salzbre...
Hypothesis is a python property based testing f...