bzh027
New Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
How do you organize script units? Do you follow any public standards or best practices?
I recently started working with Testcomplete (specifically the web module) after a long hiatus with even basic scripting, and this is my first foray into the QA space (aka I'm a newb). I've never had to follow any programming standards or worked with a large QA department. I'm looking for suggestions on how to keep script units organized. Here is my plan for now: Create stand alone script units with single functions, not tied to QAComplete for things like login, logout, and other components. Create loop script units for multi browser testing, and data driven loops. Create 'Test' script units for individual tests based on our QAComplete test plans, that call the functions from the loop scripts and stand alone scripts, passing parameters as necessary. I would link these to the test plans in QAComplete. What strategies or organizational standards do you use? Any suggestions or criticisms of my game plan?1.3KViews0likes5CommentsRe: Sending any input via keys dramatically slows down testing
Wow I restarted the application after the machine had been hibernating for some time and now it is flying. To answer the question, it was indeed independent of the application (tested on nytimes.com / browser bar input) and browser(edge/firefox/chrome), but only seemed to affect those three methods (click/clickbutton/keys). setText and all other code executed when expected. The playback description was simply 'playback' when it manifested. Changes to project options and active extensions were made but it apparently had no effect until restarting the application a couple times. I am not certain of all of the changes I made otherwise I would list them here. Thanks for the suggestions with setText, I do use that for most keyboard input.2.2KViews1like0CommentsSending any input via keys dramatically slows down testing
Hello, I've noticed that when testing web login on my application, that either sending [Enter] via keys() or click/clickbutton() dramatically slows down my testing. There is always a 5 second delay, even after reducing the default wait/delay in the project options. Is there a way to force the input any faster? I am using 12.0.122Solved2.2KViews0likes6Comments