|
|
 |
Projects
Here are some of the projects that have used Scenario Tester to save time and increase testing coverage:
• Insurance Company
Generate 70 page proposals after entering contract information. Proposals are legal documents so every word must be absolutely correct.
| Manual Testing |
Using Scenario Tester/Automated Testing |
Took one week, tested only one to three contracts and reports were only spot checked.
Staff burnout |
5 minutes to upgrade Scenario Tester with newest data
1 hour to run baseline
1 hour to run test.
Tested over 70 contracts, each time a new build was created.
Tested each contract fully. |
• Insurance Company
Mainframe Smoke Test, which made sure all screens where present with no abends and data was being retrieved correctly.
| Manual Testing |
Using Scenario Tester/Automated Testing |
| 2 hours |
7.5 minutes
Could be run remotely from home |
• Large Mainframe system – Y2K Testing
Hundreds of screens, batch processes, feeds to and from other systems, limited time and resources.
| Manual Testing |
Using Scenario Tester/Automated Testing |
| Not even attempted, impractical |
2 weeks to write all the scripts
3 days to enter and debug 250 scenarios
2 days running time to execute all scenarios
Global search and replace to change dates |
• Leasing Company
GUI system that creates leases to be imported to mainframe system
| Manual Testing |
Using Scenario Tester/Automated Testing |
40 minutes to enter lease
Very tedious and boring
New build every day plus tweaking the application all through the day |
12 minutes to enter lease
Could run complete set of 20 leases or any sub-set
5 minutes to create new leases as needed and then test them |
• Financial Institution
Used to create new scenarios for function testing and for regression testing of over 250 complex and non-sequential test cases.
| Manual Testing |
Using Scenario Tester/Automated Testing |
| In each screen, tester printed a screen shot, entered data on the screen if appropriate and printed another screen shot. Screen shot printouts were manually annotated to show the entered data and keystrokes, and were stored in a binder. This process had to be repeated for every screen in every scenario, every time it was run. |
Tester entered scenarios into Scenario Tester, including keystroke and data information. Running the scenario for the first time automatically built the baseline. This process was equivalent in time to entering scenarios manually. The scenarios could then be run again as many times as needed, very quickly.
|
• Large Manufacturing Company
Used to enter huge amounts of data into a production ERP system.
| Manual Testing |
Using Scenario Tester/Automated Testing |
In production, staff had to perform various tasks such as purging the system of obsolete purchase orders, entering the same data in more than one application, entering data stored in spreadsheets into mainframe systems.
Major drain of employee time, requiring the hiring of temps. |
All these and other tasks were automated
Increased efficiency
Decrease in needed staff resources and time |
|
|
