Background
We've a test creating files with dodgy filenames using non-utf8 chars on our test zOS machine. This causes a domino-effect of problems using the zOS machine for other use-cases.
The only thing I have to help me diagnose which test might be doing this is the file creation time.
I was hoping to do a search in the Galasa UI for this, however, Table Design only shows the submitted date (which is a bit worthless when you queue up many group runs each containing hundreds of tests).
Time frame seems to only work on submitted time also, so its not great for helping diagnose time-based issues.
I could really do with the ability to search (or at least view and sort) on the actual time the test run started, and/or ended. These values are returned in the REST calls, so the data is there to use.
Even with the REST API, this kind of fault finding is tricky - I have a time I know something went wrong, however I can't search for active runs at that time, I have to guess a from or to value because they will only capture test that have started or finished in those times
I think it would be really cool to be able to set a time period, and to be able to view all the tests that were actually running in the ecosystem within that period (whether they ended within it or not) (....in the UI!)
UI Mockup
Tasks
Background
We've a test creating files with dodgy filenames using non-utf8 chars on our test zOS machine. This causes a domino-effect of problems using the zOS machine for other use-cases.
The only thing I have to help me diagnose which test might be doing this is the file creation time.
I was hoping to do a search in the Galasa UI for this, however,
Table Designonly shows thesubmitted date(which is a bit worthless when you queue up many group runs each containing hundreds of tests).Time frameseems to only work on submitted time also, so its not great for helping diagnose time-based issues.I could really do with the ability to search (or at least view and sort) on the actual time the test run started, and/or ended. These values are returned in the REST calls, so the data is there to use.
Even with the REST API, this kind of fault finding is tricky - I have a time I know something went wrong, however I can't search for active runs at that time, I have to guess a
fromortovalue because they will only capture test that have started or finished in those timesI think it would be really cool to be able to set a time period, and to be able to view all the tests that were actually running in the ecosystem within that period (whether they ended within it or not) (....in the UI!)
UI Mockup
Tasks