What a pain it can be to reproduce issues for developers. How handy would it be if we could compile tests into an exe and pass it on for script playback? No easy request I'm sure, but I can dream...right?
A few ideas for the pot though some are a bit wacky:
1) TC packages up an exe containing project and related information as well as a target VM to run on:
- the relevant project and files i.e. it would know to grab external referenced items as well
- configuration information pointing to a shared VM (similar to what TestLeft can do)
Then when the exe is run it dynamically opens an rdp session to that VM and runs the tests in real time.
2) Alternative solution. TC standalone log viewer with script executed per action added to log.
TC currently captures screenshots per click, etc. Each screenshot is synced in the log to the line of script/Keyword test that was run at that moment. In TC you can click on this line in the log and it will instantly go to that line of script/Keyword test.
This is not possible outside of TC.
However, if there was a stand-alone TC log viewer and information was added to the current log format which showed the script that was executed at that moment then:
- A log file could be passed to the dev and,
- A new stand-alone TC log viewer could open that log that had been exported out of TC to some location for the dev (even perhaps a shared intranet website where they simply click on a link and it loads it into the stand-alone log viewer on their local PC). The dev could click on the screenshot/log entry where the bug occured. A tab in the log viewer could show the actual script that was executed at the time the screenshot was taken.
Also, assuming video recording is an option, the external standalone TC log viewer could be synced with the video such that a separate window, while the video was playing, showed the script executed at that moment.
As I said, a bit out there, but I'm guessing technically possible. Doesn't require a full runtime anywhere. Just a new standalone TC log viewer
There are a few other cons to using TestExecute for this.
1. licenses may all be in use
2. license manager is installed on a different network segment
3. developer doesn't know how to (or want to know how to) start scripts through TestExecute
@maximojo, @MKozinets, @Ryan_Moran
Have you thought (voting) for implementing video recording? For both TestComplete and (portable) TestExecute. I think that would be great improvement on demonstrating test scripts (issues) to developers. In my opinion it's doesn't test doesn't necessary have to be compiled to .exe, a video file mp4 is just as univerisal (portable) as as well and I think is much easier to implement.
Right now I use a screencapturing tool which records video (mp4 is perfectly suited), but this could be implemented in TestComplete, I think... Combine that with displaying current test step (script line no, keyword test name, etc), and some sort of logging on screen, and a timer (stopwatch) displaying on screen.
There is already a feature request for implementing video recording.
No, I have not because that is not what I was asking for. Thanks.
@Ryan_Moran Don't you think being able to handle the video recording of the executed test scenario to stakeholders (developers, etc...) would cover the same requirement?
Thanks for your suggestion.
No, I do not think a video recording is equivalent to a standalone executable playing back steps.
It does not cover the same requirement either. The primary issue is not being able to show the steps, but in very complex scenarios getting them to repeat the steps consistently, accurately, quickly, and potentially numerous times.
@Ryan_Moran I see what you mean..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.