RUDOLF_BOTHMA
Community Hero
Joined 8 years ago
User Profile
User Widgets
Contributions
Re: Run KeywordTest from imported project
Thanks Marsha_R I don't look forward to that excercise. What I am aming for at present is to drag in a KWT from a referenced project into a KWT from my own project. If you work inside your local project, you simply drag your KWT/add operation. It's at this point where I would like to put in that KWT from the referenced project. I'm not sure it can be done, but it's worth asking. Perhaps The KWTs in the referenced project need to be converted to scripts so I can call the scripts from some sort of wrapper at least ? Or perhaps I could call a KWT from a referenced project using aforementioned wrapper script ?1.6KViews0likes2CommentsRun KeywordTest from imported project
Afternoon folks. Back after a break with a new question. Our organisation has a few products, developed by different teams. Each product has had it's own development and testing. This means each product has it's own project in TC. The product I work on has dependencies on quite a few of our other products. I work on a Web application, but it depends on setup in a Winforms application. I need my KWTs to work in both, but I don't want to go redo all the work other developers/testers have already done. How do I call a KWT from a imported project in one of my keyword tests. I know for scripts, you need to duplicate it in some manner. Will I have to recreate each test with the associated object mapping and aliases to my project, or is there a way to call the Keyword test from the imported project from a keyword test in mine. I really would prefer not to have to duplicate the work other's have done and maintain changes on my end each time they modify a KWT on their endSolved1.6KViews0likes4CommentsRe: Setting Keypressing Delay from Script
What are those failures? Do they happen for every data entry or just for some certain controls? They aren't specific to any controls. Generally they happen when some control just loads a bit slower due to using a different dataset in one of the grids on the page etc. With DevExpress in Webforms, typing too quickly sometimes breaks combobox lookups, which is why that must be .Keys() with keypressed delay > 0. We create add-on software. That means we are quite dependent on how the original software fires and handles events. Sometimes it just fails for reasons outside of our control. /shrug Emulate user who is pasting data from the clipboard Ooh. I had never even thought of that possibility in standard testing, not just in the context of this topic. Thanks2.4KViews0likes1CommentRe: Setting Keypressing Delay from Script
Hi AlexKaras Thanks for the input. That's about what I thought - It's a shame though. My reason for trying this is to override user behaviour. Users go, "Ooh, the tests are slow, lets decrease this delay" then inevitably the tests start failing and wasting time investigating false failures. That second option will work, but, just wow, what a mess to always have to do it - calling a function for no other reason than iterating through a string to add a delay between key presses. Also users quite often use KWTs without script, so there is no way to implement this in these instances. Oh well, it is what it is. More user, um, training required.2.4KViews0likes3CommentsSetting Keypressing Delay from Script
Morning all, Quick question this morning. I'm trying to enforce a minimum key pressing delay in my projects because I just find that too often, the key pressing delay is zero, which causes tests to fail unnecessarily. All I want to do is go: if(key pressing delay < 10) { key pressing delay = 10; } there is Options.Run.Delay, but that sets the delay between commands, not key presses. Is there a line of code for the key presses equivalent ?Solved2.7KViews0likes6CommentsRe: wItemCount and WaitProperty
tristaanogre wrote: I try to NEVER store on-screen objects in global variables I recall doing it in the really early days of my TC development. In the end I always had to refresh & refetch the object everytime, so there was no gain in doing it this way - even a bit of a perfromance loss. Wait methods in local scope or at least within the local functions where the most reliable and efficient2.6KViews1like1CommentRe: wItemCount and WaitProperty
This is a error: The window with the 0x00010800 handle exists but did not respond during the auto-wait timeout (150 ms) This error raised because ListView.wItemCount is not ready. This could perhaps mean that TCs pointer to the object still exists, but that the item it was pointing to was destroyed, recreated or disposed in some way. If this is the case, the pointer ha changed and you will have to refresh your object and fetch again. TC will never find the property even though it thinks it can see it, since that is an old handle2.9KViews2likes6CommentsRe: wItemCount and WaitProperty
In that case, you could use the .Exists rather than trying to use a property of the object which may or may not exist e.g. var objtectExists=false; var counter = 0; while(counter<100 && !objectExists) { counter++; if(Object.Exists) { objectExists = true; break; }else { Delay(100); ObjectParent.Refresh(); ObjectParent.FindChild("objectname"); //Or similar find method // } }2.8KViews2likes10Comments