Why Automated Testing?
- Changes require thorough retesting
- Full regression tests are not practical
- Ability to execute more tests in less time
- Improve overall solution quality upon delivery
When tasked to deliver high-quality software solutions, effectiveness and efficiency of testing are often mutually exclusive. The more in-depth the testing, the more time that is potentially lost. Automated testing presents a solution to that problem, but most automated testing tools are rigid in design. Minor applications changes create a massive amount of work to maintain traditional automated test cases, often times being cast aside and thus rendering scripted tests useless.
From its inception, TestLead was designed to solve many of the common problems that companies face when trying to deploy and maintain their WMS. With its easy-to-use graphical interface, users can build scenarios quickly without any scripting or coding skills. Most importantly, as your systems evolve, so does TestLead.
- REUSABLE: Every level of the testing structure can be re- used for any facility or application instance: Actions, Steps, Scripts & Scenarios
- EASY-TO-USE: Build tests quickly with a drag-and-drop graphical interface
- DYNAMIC: Dynamically generate template-based XML, flat, or CSV files to create data such as Distribution orders as well as simulate MHE messaging
- INTELLIGENT: Use SQL statements to determine values; create conditional logic using FOR, IF, and WHILE controls
- COMPLIANT: Screen-capture during execution to build training or test execution documentation for compliance purposes
- SCALABLE: Entire test sets can be copied and modified if necessary to run on another instance or a new facility
- VALIDATION FOCUSED: SQL-constructed validations to validate results after each step
- CONCISE: Configurable reports that share summary and detail-level results of identified test failures
How It Works
At the core of TestLead is a set of building blocks called Actions. Actions enable the system to execute activities a human does several times a day: open a URL, click a specific UI button, or enter a value on an RF terminal.
An Action is the primary component of a Step. A Step provides the Action with the relevant information it needs to execute, such as which URL to open, which UI button to click, or what value to enter into an RF terminal.
A set of Steps create a test Script. A Script is a series of steps combined together to complete some logical task or test, such as stocking inventory or picking an order.
A group of Scripts are then combined into a Scenario. A Scenario often times represents all of the tests associated to a functional area, such as receiving, inventory control, picking or packing.
Simulate Actions such as…
- Click links
- Submit forms
- Enter text into RF screens or the web UI
- Communicate using SSH or TCP
- Send files over FTP/SFTP
- Send HTTP requests
- Simulate RF escape sequences
- Select web elements by Text, XPath, or URL