ContributionsMost RecentMost LikesSolutionsAbility to call Services external to the site under test It would be nice to have a step type or something similar that can be added/inserted with the purpose of calling an external service for its response. An example of this would be calling a hosted test service that provides a set of customer details which you can then use in the test to avoid hardcoding values and allowing the test to be more dynamic and thus more maintainable. Another example that comes from my usage in calling out to a hosted test service that has helper functions for the tests, things like GenerateRandomString, GenerateRandomAddress, etc. these can be done via a JS validation but with no centralised storage of JS code we have them hosted external to LoadNinja and call out to it during a test. Re: Global Parameters/Databank Tom_S Another great thing to hear, this one will go a long way to making testing multiple environments alot easier 😊 Re: Implement compaund Web Test Tom_S That's great to hear, hopefully this can bring some great maintainability and re-usability to future LoadNinja scripts. Re: Implement compaund Web Test Hi Tom_S I gave it a try yesterday using the Save As feature to try and make it work but unfortunately as it currently is the best you could do is create the starting point test to copy and then record anything after that, even if its a duplicate piece. Correct me if I'm wrong and couldn't find it but the Save As can only create a new test and not copy a piece to an existing one. Other thing I hit is that it looks like all tests must start with a page navigation event which means you aren't able to create purely partial test pieces that only contain mouse, keyboard, etc events that depend on a previous piece doing the initial navigation. Hi MPunsky That's exactly right yes, to give an example from what I am migrating across from Visual Studio to LoadNinja. The way I designed our test structure there is a folder of tests called "Components", each one of these is responsible for the actual page interactions and only contain a part of a full test, e.g. Login, Open Account, Secure Messages, etc. each item encapsulation to itself and its purpose to be chained together for use. I then have a "User Journey" folder of tests which only ever call Components and never the page directly, these ones are responsible for orchestrating the whole journey under test and managing the top level items like the input data, output logging, etc. To match that up to what you said, the Components would be the Modules and the User Journeys would be the Test Script that references the Modules Global Parameters/Databank It would be nice to have a global set of parameters that can be referenced across multiple tests, I currently would want to use this to be able to replicate an ability I had in Visual Studio to set the source url at the top most level and it affect every test in the whole load test run so that I can easy swap between environments to be tested. Currently this would require me going into each individual test and editing them Re: Implement compaund Web Test Would love to have a feature like this, I am currently rebuilding our existing suite of tests from Visual Studio in Load Ninja and this is the one thing I can already see if going to be missed and will make maintaining tests harder going forwards. With all of my previous work I created it under an encapsulated approach so that I could maintain commonly used scripts, for example, a test that goes to the homepage, then logs in, opens an account and logs out would be 4 parts that could be easily maintained and then reused multiple times to make other tests like Home > Login > Logout, Home > Products, etc all reusing the same scripts that if changed I only had to alter once to update.