I don’t see any relevant information when selecting “History” of a test case within a test run, it only shows when it was created. If you look at a test case within the test case section or test plan section view you get past history of that test case (Failures and defects) but that information is not available from within the test run. This is where it’s most useful as it flags the tester that a particular test case has a history of failures. In other words I want some transparency from one test run/build to the next.
1 Answer
1Welcome to the Testiny forum and thank you for your suggestion!
So rephrased, you would like to see pretty much the same information as we show in the “Runs” tab for a test case in the “Test cases” section, right?
Currently, the History tab inside a test run shows the history of that specific test case execution, for example who set which result and when, not the full cross-run history of the underlying test case. The idea was to separate information between test cases and the specific execution to not overload the UI with information.
Right now, you need to open the test case e.g. in a separate browser tab to see that information. And I’m making this a feature request for other users to vote and give their opinion on.
If you read this request and you would also like to have this feature, make sure to vote for this topic. We do consider the number of votes for feature requests in our roadmap and priority planning.
Best regards,
Alex
So right now, if I have a testrun there is no possibility to see if previously something was wrong with test cases to be extra careful about it? I have to already know which test case was faulty or go see each TC individually? It would be great to have visual presentation of previous iterations as regression should help with tracking them. Would it be possible to just copy paste this feature of visual presentation? like somewhere on details tab above assigned to. One line with small result symbols
– m_bieUnderstood, this is what this feature request is about, I guess :-) The implementation for this one is pretty easy, the real work is figuring out where to put that information so it's easy to find, understandable and not cluttering the UI. Anyway, thanks for your feedback, don't forget to vote for this topic! Best regards, Alex
– Alex_Hoisl