search

ably / test-observability

A web app for storing and displaying information about unit test results.
https://test-observability.herokuapp.com/
Apache License 2.0
0 stars 1 forks source link

Difficult to tell which tests ran in the test observability report. #51

Open Rosalita opened 2 years ago

Rosalita commented 2 years ago

As a developer working on a project that uploads multiple junit reports to test observability server, I want to see which dashboard data corresponds to which junit report, so that I can debug failure and be certain tests are running correctly

The ably-go SDK (https://github.com/ably/ably-go) currently uses the test observability server.

On this project three different junit reports are generated. The test observability dashboard shows an Upload ID would it also be possible to show the upload file name? We run the same tests twice (once for json protocol and once for msgpack protocol) at the moment it's very difficult to identify which data is for which protocol.

┆Issue is synchronized with this Jira Uncategorised by Unito

lawrence-forooghian commented 2 years ago

The server doesn't currently accept a filename - the JUnit test report is just submitted as a Base64-encoded blob inside a JSON object. We'd need to add a field for filename / some other sort of identifier.

owenpearson commented 2 years ago

Can I suggest getting the web UI to link to the specific workflow run? It looks like we already send the run_id as part of the upload. It still wouldn't be helpful in the case of uploading multiple reports from a single run, but ably-go doesn't do this anymore so might be an easier way to get the behaviour we want?

lawrence-forooghian commented 2 years ago

@owenpearson it actually already does that, from the upload details page, e.g. https://test-observability.herokuapp.com/repos/ably/ably-cocoa/uploads/4d7ccf51-a8ed-4ef7-b0bd-8590bed474cd