This upgrade process involves the transition of testing some or all applications with the legacy tool (in most cases LR) to NeoLoad. The Neotys professional services team has developed a process, based on extensive experience, to implement this transition. The goal is to make sure the move to NeoLoad is as efficient and reliable as possible.
Modern web and mobile applications bring complexity and new challenges to the performance testing activity. Many enterprises are upgrading their load testing solutions to meet these new requirements.
PROCESS OVERVIEW
Training
Define Scope
Migration
Validation
NeoLoad Ready
• Train your team on NeoLoad
• Can be customized to meet the specific needs of your organization
• Adapt training to match your process with your existing tool
• Identify projects and scenarios in scope
• Determine testing toolset configuration
• Install NeoLoad
• Determine Strategy for migration
• Per Project: - Recapture the legacy tool scenario into NeoLoad - Optimize test design (Add variable extractors / test data & validation - Perform Runtime test configuration
• (Optional) Integrate with other tools (APM, CI, Test Management etc.)
• Run short test with a few users
• Compare to legacy tool results and determine results deltas
• Provide a basic test report
• Test all your web and mobile applications with NeoLoad
Neotys highly recommends attending a NeoLoad training course to accelerate self-sufficiency in deploying NeoLoad projects.
This training step complements the migration process by demonstrating how to handle specific legacy tool capabilities within NeoLoad. The Neotys instructors are expert load test consultants who have good knowledge of the main testing solutions on the market and can help you understand the specific differences to ease your transition.
Training can be focused on standard usage of NeoLoad or it can be adapted to your specific needs in order to bring more value to your team.
For example a focus on methodology, Rich Internet Applications etc...
If several projects are to be migrated, the priority and the sequence must be defined.
Load test scripts are only valid for a specific version of the application. In most cases modifying the existing scenarios costs more than creating a new test design with the new solution, particularly when using a GUI-based solution like NeoLoad. Depending on future releases of the applications and how they map to the test plan, some legacy tool scripts will not be included in the scope of the migration. Instead, new NeoLoad tests will be created for the next test campaign for those updated applications.
A second factor to be considered in the scoping stage is to determine if the test configuration itself should be part of the migration or not. The test configuration is defined by several parameters: Ramp up configuration, test duration, load generators, monitors.
At the end of the scoping stage, NeoLoad components will be installed to reproduce the tests done with your previous solution. During this step, we will define the best options to either reproduce or improve upon your current installation as you migrate to NeoLoad components.
PREPARING FOR MIGRATION
This stage is a critical planning phase geared to define the durations of the transition overall as well as each individual step along the way. The outcome of this stage is a Neotys proposal for the entire migration project.
The goal of defining the migration scope requires understanding of these important items:
• Global overview : Mapping organization & processes
• List all components of the legacy tool installed in your IT environment (multiple controllers, Remote monitoring, APM solution, load generators)
• Who are the individual users of the legacy tool (performance center /per project)
• How many load test projects will be migrated
• What is the size and the complexity of each project
• What are the deliverables of your load test projects (document in sequential order to prepare a load test Test plan and Tests report)
• What are the existing test processes and who is responsible for each part
DEFINE SCOPE: “MAPPING THE ORGANIZATION & PROCESSES”
MIGRATION
To ensure your success, Neotys provides consultants during the Migration stage who have the required skills to translate scripts into NeoLoad virtual user profiles.
NeoLoad Installation Steps• Installation of the NeoLoad Controller
• Installation of Load Generators
• Installation of Remote monitoring engines if necessary
• Installation of the Neotys Team Server
• Installation of the Neotys License Server
• Cloud infrastructure set-up
Each NeoLoad component will be installed to reproduce or improve upon the legacy tool architecture.
There are two primary options for the migration strategy:
1. Migration per project based on when tests are required
With this approach, each application’s test migration is handled serially. Starting with “Project 1” each of the three main tasks are completed before proceeding to the next application. The process is then repeated until all “n” projects in scope of the migration have been completed.
2. Migrate all test preparation activities for all applications at the same time
• Project 1 Preparation
• Project 2 Preparation
• Project n Preparation
Test AnalysisTest Preparation Test Execution
• Project 1 Execution
• Project 2 Execution
• Project n Execution
• Project 1 Analysis
• Project 2 Analysis
• Project n Analysis
With this approach, each task type Phase of the migration is completed for ALL application projects in scope before moving on to the next task type…e.g.
“Preparation” tasks are completed for all applications prior to moving to “Execution” tasks etc….
For both options, the applications must be available to capture traffic and the test data used in legacy tool scripts must remain valid. Most customers find the first option easier because the migration only starts when the team involved is ready. Also the planning is more flexible and it facilitates the learning of NeoLoad by your team.
Scripts Estimated migration duration:
• For simple scenarios, the conversion takes a few hours (2 hours usually). A simple scenario is composed of a maximum of 20 steps with no specific development on the client (Specific C functions in legacy tool script)
• For the most complex scenarios, migration could take a full day
Migration prerequisites:
• The environments must be available to test the old scenarios and the new ones for each application
• The scripts that are in scope for the migration project must be valid and executable before starting the process of creating NeoLoad virtual users. Only valid scenarios will be rewritten. A valid scenario means that the scenario execution doesn’t show any errors and the function is completely executed in the application
NeoLoad lets us test in 1 day what previously took 5 days with [our legacy tool]. Now we can do performance testing every sprint without holding up the release. - Andreas Papadopoulos, Head of Software Delivery, The Sporting Index
“”
NeoLoad was chosen because of the balance of functionality, ease of use, and cost…[our legacy tool] employs a completely unreasonable pricing model. - Brian Daniel, Sr. QA Engineer, ICW Group
“
”
We did enjoy a cost saving when we made the switch to NeoLoad, but perhaps more importantly we were able to reduce our risk when releasing new software. By generating larger numbers of virtual users and through its support of the PUSH technology, NeoLoad enabled us to construct much more realistic load scenarios. - Adam Dance, Head of QA, IG Group
“
”
Runtime Test ConfigurationNeotys consultants will analyze the configuration of the controller to prepare the test scenario using the following parameters:
The duration of this step depends upon the complexity of the tests requiring migration.
Integration With Other SolutionsNeoLoad scenarios can also be integrated with other solutions. The duration and the level of the integration depends upon the solution in question. Examples of potential integrations include:
• Integrate NeoLoad test in your test reference solution
• Integrate NeoLoad test results into your test reference solution (storage with report publication in a different format)
• Integrate NeoLoad test into your Continuous Integration solution to automatically launch load tests
• Integration with APM
VALIDATION OF THE MIGRATION
A test with a few users will be launched on each project to validate the success of the migration. NeoLoad response times will be compared to the response times computed from previous test results and any deltas will be investigated.
The automatic report generated by NeoLoad at the end of the test will be used to validate the success of the migration for each project.
VALIDATION OF THE MIGRATION
All of your web and mobile applications’ performance testing projects are now ready to be handled with NeoLoad!
By using the Neotys testing process combined with NeoLoad you will experience an increase in your team’s productivity effective immediately.
![Adodb Scripts And Some Sample Scripts[1]](https://static.documents.pub/doc/80x56/558c78c9d8b42a566c8b4732/adodb-scripts-and-some-sample-scripts1.jpg)
