Been asking for this feature for a long time now...
Posted: Thu Jun 18, 2015 5:35 pm
I've asked in seminars, via email and possibly on the board as well, I can't remember.
But I'm asking again. Admittedly something of a work around was offered a year or two ago, but that was at a different company and the code has been lost to me. It would be preferable to have a baked in piece of code anyway.
Here is my scenario, I can't imagine it's that uncommon:
I have a test that's very large, it takes about 4 hours to run. It's 400 iterations. In this case, the test started at 12:23p. According to the logs there was a failure at 2:43p - how do I find the corresponding test?
This should be trivial, but with Ranorex it's prohibitively difficult, and it should not be. This should be basic reporting functionality.
If you look at the test summaries, each line only shows you the duration of the test iteration itself (it's debatable how useful that is). So I have to expand all four hundred tests, look at the time for each of them, and then do some time based math in my head adding the start time, to the time in the test to try and estimate what it is. This seems silly to me.
There's no easy way to line up a time in an event log, or other log with your test. If a developer says to me, did your test fail at the time we see the log failure I can't quickly (or even that easily) answer that question because our tool doesn't show the time the test executed.
I feel foolish saying that. I've brought Ranorex to two companies now and this feels like a real fundamental flaw in the reporting that should easily be fixed. It seems like a case where the product isn't being used in a real world scenario by those who develop it.
Apologies if my rant seems harsh, but it's a point of frustration for me, I hope that this simple feature can be implemented so events can easily be lined up with test results in the future - I don't want to have to tell developers or business people I'm not sure which test caused the failure because the time isn't displayed on the report (or take a whole bunch of time to figure that out).
Thanks for considering my request.
But I'm asking again. Admittedly something of a work around was offered a year or two ago, but that was at a different company and the code has been lost to me. It would be preferable to have a baked in piece of code anyway.
Here is my scenario, I can't imagine it's that uncommon:
I have a test that's very large, it takes about 4 hours to run. It's 400 iterations. In this case, the test started at 12:23p. According to the logs there was a failure at 2:43p - how do I find the corresponding test?
This should be trivial, but with Ranorex it's prohibitively difficult, and it should not be. This should be basic reporting functionality.
If you look at the test summaries, each line only shows you the duration of the test iteration itself (it's debatable how useful that is). So I have to expand all four hundred tests, look at the time for each of them, and then do some time based math in my head adding the start time, to the time in the test to try and estimate what it is. This seems silly to me.
There's no easy way to line up a time in an event log, or other log with your test. If a developer says to me, did your test fail at the time we see the log failure I can't quickly (or even that easily) answer that question because our tool doesn't show the time the test executed.
I feel foolish saying that. I've brought Ranorex to two companies now and this feels like a real fundamental flaw in the reporting that should easily be fixed. It seems like a case where the product isn't being used in a real world scenario by those who develop it.
Apologies if my rant seems harsh, but it's a point of frustration for me, I hope that this simple feature can be implemented so events can easily be lined up with test results in the future - I don't want to have to tell developers or business people I'm not sure which test caused the failure because the time isn't displayed on the report (or take a whole bunch of time to figure that out).
Thanks for considering my request.