Now there’s a better way to automate functional QA testing, regression testing, load testing and performance benchmarking for your Remedy applications! Load Challenger uses XML to create repeatable test scripts, launch functional and performance tests from multiple clients, produce detailed test logs and capture all test anomalies, quickly and easily. And because test scripts can be repeated on demand, prototype testing, formal acceptance testing and post-upgrade/post-enhancement regression testing is a snap!
Load Challenger is specifically designed for testing modified out-of-the-box applications or built-from-scratch customized applications.
|
|
A consistent and repeatable software testing process plays a key role in ITIL, CMM, ISO 9001 and Six Sigma methodologies. If your Remedy applications are part of a quality initiative, you should be evaluating Load Challenger as your primary Remedy application testing tool.
Not running a formal quality initiative and therefore don't believe you need a Remedy testing tool? You probably still need to improve your Remedy application testing process. Check out our 5 Top Reasons for using Load Challenger to automate Remedy application testing.
|
Typical Uses
Use Load Challenger to automate your repetitive testing activities (particularly QA testing and regression testing), stress test your Remedy application (and network infrastructure) and establish performance benchmarks for local and remote users. It excels at all those testing tasks you dread and your QA team probably dreads even more. Some illustrations:
|
|
SAMPLE APPLICATION #1:
Team "A" plans to make their Remedy application available to a wider user audience, but is concerned about application performance and overloading the existing Remedy servers. Load Challenger makes it an easy task to measure performance and verify proper server/network sizing. And if there's a problem, Load Challenger captures the necessary metrics to justify additional IT infrastructure capital expenditures.
- Use Load Challenger to record test procedures for each of a multitude of application functions
- Have Load Challenger run all test procedures with multiple "virtual" clients, thus simulating anticipated user workloads
- Repeat the above step from remote offices and/or remote sites (over your local-area network, or over your wide-area network)
- Analyze Load Challenger's performance reports and make software and/or infrastructure adjustments where necessary
- Repeat the above steps until acceptable performance is observed in all locations
- After deployment, periodically repeat some or all of the above steps to monitor application performance and ensure all features continue to function as designed
|
|
Click on any highlighted activity below
|
Requirements Gathering
|
|
Design and Validation
|
|
Prototyping and Development
|
|
Functional QA Testing
|
|
Regression Testing
|
|
Stress Testing / Load Testing
|
|
Performance Benchmarking
|
|
Deployment and Documentation
|
|
Ongoing Application Monitoring
|
|
SAMPLE APPLICATION #2:
Team "B" is planning to upgrade their Remedy AR System and Windows operating system. They want to verify that all past functionality is retained after these upgrades, before turning the application over for company-wide production use.
- Use Load Challenger to record test procedures for each of a multitude of application functions
- Have Load Challenger run all test procedures, thus establishing a "pre-upgrade" functional test baseline
- Have Load Challenger re-run all test procedures with multiple "virtual" clients, thus establishing a "pre-upgrade" performance baseline
- Perform the Remedy and Windows OS upgrades
- Following the upgrade, have Load Challenger perform regression testing by re-running all previous test procedures, to verify all past functionality has been retained
- Note differences between these results and your pre-upgrade functional baseline, make software and/or infrastructure adjustments where necessary, and have Load Challenger repeat this process
- Use Load Challenger stress test the new system by re-running all previous test procedures with multiple "virtual" clients, to verify past levels of performance have been retained
- Note differences between these results and your pre-upgrade performance baseline, make software and/or infrastructure adjustments where necessary, and have Load Challenger repeat this process
- Have Load Challenger establish revised performance benchmarks
- After deployment, periodically repeat some or all of the above steps to monitor application performance and ensure all features continue to function as designed
|
|
Click on any highlighted activity below
|
Baseline Functional QA Testing
|
|
Baseline Performance Testing
|
|
AR System Upgrade
|
|
Server OS Upgrade
|
|
Regression Testing
|
|
Stress Testing / Load Testing
|
|
Performance Benchmarking
|
|
Deployment and Documentation
|
|
Ongoing Application Monitoring
|
|
SAMPLE APPLICATION #3:
Team "C" plans to enhance their Remedy application by making some changes to selected forms and workflow, but they also want to make sure all previous features are retained.
- Use Load Challenger to record test procedures for each of a multitude of application functions
- Have Load Challenger run all test procedures, thus establishing a "pre-upgrade" functional test baseline
- Have Load Challenger re-run all test procedures with multiple "virtual" clients, thus establishing a "pre-upgrade" performance baseline
- Deploy the application enhancements in incremental steps
- Use Load Challenger to create and run test procedures on all new features
- Have Load Challenger re-run all past test procedures to ensure that all past features have been retained
- Have Load Challenger run all test procedures with multiple "virtual" clients, thus simulating anticipated user workloads
- Repeat the above step from remote offices and/or remote sites (over your local-area network, or over your wide-area network)
- Analyze Load Challenger's performance reports and make software and/or infrastructure adjustments where necessary
- Have Load Challenger establish revised performance benchmarks
- After deployment, periodically repeat some or all of the above steps to monitor application performance and ensure all features continue to function as designed
|
|
Click on any highlighted activity below
|
Enhancement Request Gathering
|
|
Baseline Functional QA Testing
|
|
Baseline Performance Testing
|
|
Prototyping and Development
|
|
Functional QA Testing
|
|
Regression Testing
|
|
Stress Testing / Load Testing
|
|
Performance Benchmarking
|
|
Deployment and Documentation
|
|
Ongoing Application Monitoring
|
|
SAMPLE APPLICATION #4:
Team "D" plans on developing a new AR System-based application from scratch, wants to follow the recommended software practice of developing new applications in incremental steps (or "builds"). They need an automated tool for functional testing and performance testing.
- For each incremental build:
- Use Load Challenger to record test procedures for each new feature implemented
- Have Load Challenger run all functional QA test procedures to verify the application behaves as intended
- Have Load Challenger perform regression testing by running all previous test procedures, to ensure that all past features have been retained
- As appropriate, have Load Challenger run all test procedures with multiple "virtual" clients, thus simulating anticipated user workloads
- Repeat the above step from remote offices and/or remote sites (over your local-area network, or over your wide-area network)
- Repeat the above five steps until the primary application development effort is completed
- Supplement release candidate testing by having Load Challenger re-run all test procedures, to verify the application meets all functional and performance acceptance criteria
- Have Load Challenger establish baseline performance benchmarks
- Supplement final user acceptance testing by having Load Challenger re-run all test procedures
- After deployment, periodically repeat some or all of the above steps to monitor application performance and ensure all features continue to function as designed
|
|
Click on any highlighted activity below
|
Requirements Gathering
|
|
Design and Validation
|
|
Prototyping and Development
|
|
Incremental Functional QA Testing
|
|
Incremental Regression Testing
|
|
Stress Testing / Load Testing
|
|
Release Candidate Testing
|
|
Performance Benchmarking
|
|
Final Acceptance Testing
|
|
Deployment and Documentation
|
|
Ongoing Application Monitoring
|
|
Features
- Records and stores test procedures as repeatable XML scripts
- Launches test scripts as a single user or as several "virtual" users
- Any number of test clients can launch tests, from any location
- Captures detailed information on application behavior and performance
- Displays test status while in progress
- Writes complete log files for later analysis and reporting
- Designed specifically for Remedy AR System-based applications
Benefits
- Automates regression testing for incremental prototype builds and full-scale application development efforts
- Creates a library of "standard" production test cases, thus enforcing consistent and complete unit testing, integration testing, regression testing, functional QA testing and final user acceptance testing
- Offers both application stress testing (increased traffic from the same user base while the host server is already busy) and load testing (increased traffic from additional users while the host server is already busy)
- Measures true end-to-end response times and establishes accurate performance benchmarks, even over wide area network (WAN) connections
- Streamlines formal recertification testing and performance benchmarking following a server OS upgrade, AR System upgrade, Remedy ITSM suite application upgrade or Remedy application enhancement
- Works with all Remedy applications, whether "out of the box" ITSM suite applications, customized ITSM suite applications, or custom applications built directly from the AR System
For More Information . . .
Please call or send us an email to learn more about Load Challenger, arrange a webcast demonstration or register for an evaluation license.
|
