This is stupid. Why coded steps aren't recorded in storyboard? I want to export test steps as html, and see screenshots on every test action was made. But to my surprise, for some reason, apparently you can't see coded steps screenshots. Why?
What if i want to see what was done in sequence of test actions? My coded steps has some simple randomization in entering text.
UPDATE:
2. [RegistrationTest_CodedStep] : Enter text 'ZENKLOPAVADINIMAS' in 'BrandNameText'
here is what i see in exported result. it does not even enter "zenklopavadinimas" in that field.
p.s. i am using test studio.
10 Answers, 1 is accepted
It's definitely one I would enjoy having available, as I have a lot of coded steps.
Please like and comment on those in the feedback portal. The more attention they receive, the more likely we will see them in future builds.
What screen shot would both of you like to see put in the storyboard for coded steps? Keep in mind when you click "Script Step" or "Customize in code":
- There may be no browser open at all.
- The browser might be on the wrong screen.
Cody
Telerik
I almost forgot to mention, the description that is put in the storyboard for coded steps comes directly out of the code. See the two attached screen shots for how this works. This allows you to make it anything you want.
Cody
Telerik
Just like is posted at http://feedback.telerik.com/Project/117/Feedback/Details/60855-add-custom-screen-shot-to-storyboard, my main concern is alert dialogs or any other dialog that is being handled by a custom dialog handler. If we launch a new browser and connect in code, then take a screenshot of a section, that would also be nice to be able to add to the StoryBoard.
Just my thoughts.
Even so if that "coded(scripted) step action" isn't doing everything at all to a browser window, can't it have additional option to select if i needed a screenshot?
Whats the purpose of that storyboard if it only can capture non scripted step? If i am testing for example registration form? I don't think i am going to use static data. i am also not going to use any data from external sources, because i have for that random input generators, and i want it to be as more dynamic it can be.
Reporting is not only for a tester who wrote a test. It should be way more informative. If it was scheduled test somewhere on the server? How else will i know what was doing during that test? Maybe something unexpected occurred? What if a client want's to see test results? he is going to read that all codish step gibberish?
I think you guys are very smart. I don't think i should waste any time raising questions. It is quite simple and obvious.
I think you both are fully aware that coded steps are a very powerful feature of Test Studio. What you can do in a coded step is only limited by your programming skills. The code can easily be doing something that doesn't even interact with the application being tested (in a browser or a WPF application). When that is the case, obviously it doesn't make sense to automatically take a screen shot of the application because that wouldn't represent what the code is trying to do.
Another complication is the code can easily be interacting with multiple screens of the application. We have a technical limit of one screen shot per test step, which means we can't add multiple screen shots of multiple pages for the one coded step.
For all the above reasons we chose to not automatically take a screen shot... it would be wrong too often. But it does make very good sense to give you the ability to insert your own custom screen shot/image of your own choosing for your coded steps. That's what the feature request is all about. I am hopeful we'll be able to implement this feature in the near future.
Cody
Telerik
Hi Cody,
Any updates on this request?
Rgds,
Fairuz
I'm assuming you're referring to this feature request? No there has been no progress on this one. At this time we have too many other higher priority features we're working on, such as mobile testing.
Regards,
Cody
Telerik