Contributions
Re: Consistency running test suites in Test Complete vs. Test Execute
Two quick follow up questions: 1. Why is adding delays neccessary for the automation to run properly? i.e. does TestComplete/Execute have the equivalent of a document on load or on ready listener it uses to check for page resources, DOM elements, etc. to complete loading? 2. Assuming no changes to a site and a static group of well written fully passing tests, is the expectation of a recurring 100% success rate reasonable?1.4KViews0likes1CommentConsistency running test suites in Test Complete vs. Test Execute
Greetings, I am curious if anyone has noticed differences in test consistency between Test Complete and Test Execute. Currently our organization's work flow consists of creating groups of keyword tests and scripts in Test Complete on a dedicated QA machine. These tests are then run via Test Execute on a second decidated QA machine. We are currently running a core group of tests in stage and development enviroments and on three browsers(chrome, edge, firefox.) These suites are run twice a day. However we are having some issues achieving a baseline of 100% success. When run in Test Complete, the suites pass with 100%. However, when running the same suite in Test Execute approximately 5-15% of tests fail. Has anyone else noticed anything similiar? The types of failures and particular failing tests are not always consistent from browser to broswer or production environments.Solved1.6KViews0likes4Comments