Forum Discussion
Thank you Hassan_Ballan for your reply.
"Log Message" or "Post Screenshot" are new keyword test steps, then. - How could I assign the result (= a screenshot) to the existing test step 'Run Script Routine'?
For example, if I had 20 test steps of type 'Run Script Routine', inserting 20 test steps of type 'Post Screenshot' becomes quite confusing. Isn't there a simpler solution?
Thanks in advance
- Hassan_Ballan2 months agoContributor
If I understand it correctly that you are trying to use screen shots to document test steps, may I suggest using a different approach.
Use the simple "Log Message" or create a log folder structure for the test case hierarchy by utilizing the Logging Operations "Append Log Folder" along with "Pop Log Folder" Logging Category | TestComplete Documentation (smartbear.com)
- sborno2 months agoOccasional Contributor
Yes, I try to document test steps as clear as possible and like to illustrate them by a screenshot taken at the time of design.
I'll think logging is not a adequate solution, because this will be done during the execution of each test step and if I understand it correctly, it is not visible in the flow of the keyword test table.
Is there a way to get the same behaviour for a step of type 'Run Script Routine' as when processing a normal keyword test step by using a plugin for Testcomplete or something like that?
Is there a possibility to develop a plugin for Testcomplete to reach this goal?- Hassan_Ballan2 months agoContributor
"Is there a possibility to develop a plugin for Testcomplete to reach this goal?"
You can reference this https://support.smartbear.com/testcomplete/docs/working-with/extending/custom-plugins.html
Related Content
- 12 months ago
Recent Discussions
- 10 hours ago
- 11 hours ago