Champion Level 3Try one of these:
Thanks, Marsha. I think our investigation and posts have overlapped. Have a look at what I found a few minutes ago. The options you suggested add the commands to the Keyword Test itself, which then have to be run, and then removed after and replaced with the results of the command.
DesignTimeActions are installed directly into the toolbar menu where Clipboard Checkpoint and Manual Checkpoint are provided, and can run from there.
Still the only result I see is a pop-up with script syntax and no way to paste it directly into the Keyword Test.
Just to be clear, I'm making sure that I fully understand what is possible so that I can knowledgeably declare it as totally unacceptable.
Having said that, I'm happy to have learned about DesignTimeActions. I haven't thought of any use for them yet in our environment but maybe I will.
rickm wrote:
Thanks, Marsha. I think our investigation and posts have overlapped. Have a look at what I found a few minutes ago. The options you suggested add the commands to the Keyword Test itself, which then have to be run, and then removed after and replaced with the results of the command.
DesignTimeActions are installed directly into the toolbar menu where Clipboard Checkpoint and Manual Checkpoint are provided, and can run from there.
Still the only result I see is a pop-up with script syntax and no way to paste it directly into the Keyword Test.
Just to be clear, I'm making sure that I fully understand what is possible so that I can knowledgeably declare it as totally unacceptable.
Having said that, I'm happy to have learned about DesignTimeActions. I haven't thought of any use for them yet in our environment but maybe I will.
As noted, instead of design time actions, look into creating Keyword Operations in your script extensions. These will show up in the keyword editor and allow you to build your custom checkpoints that way.
Thanks again, tristaanogre.
Probably because I don't fully understand yet, but it seems that we are not on the same page.
The runtime extension that I call assembles I think what you call a keyword command that is inserted into the keyword test, complete with all the arguments which I have determined from the runtime state and options selection in the UserForm when applicable.
If I build a keyword command, the functionality that I see is that I could stop recording, drag my custom command into the keyword test at the stopped location, and then what? Typically a form pops up and one has to enter all the argument values. For example, drag and drop "Delay" into the test.
Are you saying that my code could fully parameterize the keyword command and end by the full command being dropped into the keyword test?
I found it in the documentation, "Custom keyword test operations", and just looking at it now...
I haven't built a keyword operation into an extension yet... but the theory is there that, yes, you could do as much as you want to with a keyword operation so that it could simply drag into your keyword test fully formed, depending upon how much code you write in the extension.
tristaanogre wrote:I haven't built a keyword operation into an extension yet... but the theory is there that, yes, you could do as much as you want to with a keyword operation so that it could simply drag into your keyword test fully formed, depending upon how much code you write in the extension.
If all goes well I'll look at this too because it could be useful for other purposes. This would be the best-case replacement for the record-time extensions, but I can say now that it's just not acceptable. I'm really counting on them keeping record-time extensions. Can you imagine the reaction I'll get if I suggest we continue to pay yearly maintenance for Test Complete when I have to replace the existing 2 or 3 mouse click operation with the work-around that we've discussed in this thread? No, I'd be recommending an alternative testing strategy (not that I have one yet).
A question for anyone: If we stick with v12.20, and of course stop paying yearly maintenance, how long do you think we could continue before TC stopped working due to changes in Windows, hardware, etc? We could leave it all on Windows 8.1 but eventually (soon) we'd want to be testing on Windows 10 if that's what our customers are using. I had just started creating tests for a 2nd product. I have 62 now but it will lead to another 1000. I've had to put it on hold.
