When developing UI tests or investigating bugs (in tests or app) its sometimes very helpful to see what the browser is doing, specially when the test works locally but fails in CI.
We lose a lot of time just investigation those issues by guessing what the problem might be.
Highest priority is to have video recordings of failed tests, having all test runs recorded would be nice but not very important.
Also to save storage the recordings could only be made when a specific switch is set in the .drone.yml. When the developer faces an issue, she could set that switch and get the recordings for analysis.
Some work was done by @patrickjahns on this topic:
https://github.com/patrickjahns/vncrecordingserver
alternative we could use the recording feature of https://opensource.zalando.com/zalenium/#usage
CC @patrickjahns @phil-davis @PVince81
When developing UI tests or investigating bugs (in tests or app) its sometimes very helpful to see what the browser is doing, specially when the test works locally but fails in CI.
We lose a lot of time just investigation those issues by guessing what the problem might be.
Highest priority is to have video recordings of failed tests, having all test runs recorded would be nice but not very important.
Also to save storage the recordings could only be made when a specific switch is set in the
.drone.yml. When the developer faces an issue, she could set that switch and get the recordings for analysis.Some work was done by @patrickjahns on this topic:
https://github.com/patrickjahns/vncrecordingserver
alternative we could use the recording feature of https://opensource.zalando.com/zalenium/#usage
CC @patrickjahns @phil-davis @PVince81