It would be nice to have the story board capture subtest screenshots instead of the "Test Step" placeholder. It would be fine maybe to watermark the screenshots with "Test Step," but still show the screens for reference.
Posted on:28 Sep 2020 14:44
Thank you Iliyan for your encouraging answer!
We are eagerly waiting to see this much desirable and highly valuable feature being incorporated in Test Studio!
Posted on:21 Sep 2020 10:56
Hi, thank you for the feedback and the additional details. We are currently planning our roadmap and Storyboard improvements are something that we will consider. In the next few weeks, we will have more clarity. I will update you as soon as I know if and when are we going to work on the Storyboard enhancements.
Thank you for your time and understanding. I appreciate it!
Iliyan PanchevProduct Manager, Telerik Test Studio
Five days of Blazor, Angular, React, and Xamarin experts live-coding on twitch.tv/CodeItLive, special prizes, and more, for FREE?! Register now for DevReach 2.0(20).
Posted on:14 Sep 2020 14:15
When customers (particularly from regulated industries) ask to see what tests were planned and/or carried out, it is impractical to show a Storyboard with many "Test as Step" screenshots. To answer your question, the Storyvoard should be fully expanded with all steps (numbered with description and images), perhaps according to a checkbox when Exported to HTML.
For example, if a "Master Test" had 2 genuine steps and "Subtest 1" as a step (for a total of 3 steps) and "Subtest 1" itself had 3 steps and "Subtest 2" as a test step (for a total of 4 steps), and "Subtest 2" itself with 5 genuine steps, the expected Storyboard for "Master Test" would show a grand total of 10 steps as follows:
2 genuine steps from "Master Test"
3 genuine steps from "Subtest 1"
5 genuine steps from "Subtest 2"
When "Master Test" is executed, all 10 genuine steps are executed in the defined sequence and so, the steps need to be exported and numbered in actual execution order.
To recap, the Storyboard must be exported down to the genuine test level, recursively replacing all "Test as Step" steps encountered in the full sequence. Another way to look a t it is that we need the placeholder steps to be replaced by the actual steps when exported to HTML.
After all, our customers want to know what is being executed...
Posted on:27 Jan 2017 02:46
We would like this feature as well. If the storyboard does not show for subtests, the subtests feature is pretty much unusable for us. Are there any plans for it?
Posted on:05 Feb 2016 13:42
I would also like to see this feature. Most of our tests are made up of subtests and we would really like to see the storyboard capture there.
Posted on:22 Apr 2014 14:02
In addition - After you double click on an IF/Else step you should be able to see the steps inside the IF.
Posted on:21 Aug 2013 13:06
From my perspective, they all should be displayed. Maybe watermarked with the "sub-test" name. Also, maybe it is just a bug or a fluke, but when I record the test and move out the steps to a sub-test, the storyboard shows a graphic with a large, red "X" for it as if it could not record the screenshot. At any rate, it is nice to be able to have subtests for the purpose of reuse. However, if aggregating several subtests into a large, regression test, the story board is ineffective if it simply shows a series of screens marked to a subtest name. It is also impractical to print storyboards for every subtest as it loses cohesion to the full, regression test.
Posted on:21 Aug 2013 11:49
The storyboard displays the expected image at this point of the test, the step in particular. A test as step though includes multiple test steps. Which image should be displayed there?