Address the need to achieve rapid test automation.
Code-free is at least 2 to 3 times more productive when compared to a coded approach. Without the need for high cost, specialised automation engineers TestDrive tests browser, client/server and legacy applications. Its device emulation support even enables you to test responsive web applications designed for mobile devices.
TestDrive’s unique ability to check every element of every screen makes it the only viable way to run a full regression test.
Result: higher quality applications, delivered to market in a shorter period of time.
Playback timing, screen shots, analysis of all the visible and invisible screen elements are all handled automatically by TestDrive, letting you concentrate on the testing !
Patented technology allows screens, content and input actions to be presented in a way every user can understand. In playback it means scripts will continue to execute even when the contents of a screen or page have been re-arranged.
Span multiple applications and technologies in a single test. Use a browser to buy a widget, process the order in SAP and fulfill it in a green screen application.
Automatically retrieve the full content of each screen as it appears. This means that all the data is available to be tested, or used in processing. E.g. in a combo box verify every item rather than just the single item selected.
Automatically adapts to application change or gives the user the opportunity to dynamically amend the areas that need attention.
Data driven tests are fundamental to expanding test coverage. Use spreadsheet data to override the script input values, to act as values to verify against and even update columns so that the values can be used later in the test.
Uniquely TestDrive separates the instructions as to how to navigate an application from the logic, tests, data drivers and success criteria. If the application under test changes significantly and the navigation has to be replaced, it ensures that the business logic survives.
Users select which checking rules are to be verified as an automated test executes. These include base-line comparisons, specific content, spell-checks, link checks, hardware impact checks and performance checks.
All information including screen shots, content analysis, errors, mark-ups and performance data from a test execution is stored as part of a Test Result. This information can then be analysed in numerous ways within the Result Viewer.