Hello,
I am working with the Regression Suite Automation Tool right now and I've read the documentations, but I still haven't found an answer to my question.
Is there a way to use one test case in a loop, and in every loop it uses another variable from a list and iterates all entries?
Example: I want to test the creation of a sales order with different payment methods, payment terms, accounts and products. The steps are the same every time, but I want to test every possible comibination of all these parameters, so there will be hundreds of possibilities.
Of course I don't want to create all cases one by one or copy it and change the parameters manually. I want RSAT to iterate through those combinations and fill them into the parameter file, then loop through the test again.
Sample list like this:
Thanks in advance!
Is there a way to add a list of parameters to the RSAT runs?
I am new to this and struggling to find the commands to configure and run the test cases from powershell, In microsoft documentation I found the code but actually not able to run the test cases.. docs.microsoft.com/.../rsat-tutorial , how can we connect to RSAT using powerShell ?
[/quote]There's an example here (near the bottom of page): https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/perf-test/rsat/rsat-tutorial#advanced-scripting
This is what i used when I started with powershell and RSAT
I am new to this and struggling to find the commands to configure and run the test cases from powershell, In microsoft documentation I found the code but actually not able to run the test cases.. docs.microsoft.com/.../rsat-tutorial , how can we connect to RSAT using powerShell ?
Mateusz Lukowiec Thank you for this suggestion and I actually recommended your tool internally as I already tested it in the past and was very satisfied with it. Unfortunately this was no option for the project. But I do recommend your tool whenever I have the chance.
markmj Thanks for all your answers and efforts, I'm sure there would be another way and maybe it's even better for some projects. Maybe this thread and your answers will help some people in the future
Hi Marvin Hehlert, have you looked at any RSAT alternatives?
RSAT is a fine tool to use if your project is small and the number of test scripts is <100. The bigger the project and the more test scripts you have, the more of a maintenance and management nightmare it is.
Here is a 2,5-year-old video showing such an excel loop inside a test script in a tool that we and many of our clients use for test automation projects, Executive Automats - www.youtube.com/watch
[/quote]you work for Executive Automats, right? I think you should make that clear in your profile/posts
I agree, but if the tests are required (there's no option NOT to do them), I think it's a better approach. When I ran my test with 51 PO's, 7 failed, so it's easy to see which run failed and easy to tell from the steps and results, which values were used in the failed test. It would be great to see them as separate tests, but I can't think of a solution for that right now.
If separate tests were required, I'd go the route of using a tool to create/modify parameter files for a set of derived tests.
I looked at executive automats (have an active trial) and it's a good tool:
The excel loop function is great
The task recorder is way better, especially when it comes to editing recordings
Has conditional steps (e.g. dialog may or may not appear)
Can do negative tests
Much more extensive comparison options (can use code)
Negatives
Pricey - about $20k per year for SaaS
Can't make task guides from recordings
If you want to change excel data files, you have to unlink all steps from old excel, replace the excel and relink steps to new excel
Can't use excel loop for parent child looping (e.g. create these PO's AND lines: I need to loop through denormalized data that has PO header and line data in 1 row)
Can't share tests with partners (unless they use it)
Hi Marvin Hehlert, have you looked at any RSAT alternatives?
RSAT is a fine tool to use if your project is small and the number of test scripts is <100. The bigger the project and the more test scripts you have, the more of a maintenance and management nightmare it is.
Here is a 2,5-year-old video showing such an excel loop inside a test script in a tool that we and many of our clients use for test automation projects, Executive Automats -
Thanks for responding, I didn't give any feedback in this post for some time now because we accepted the manual change of all varaibles. But as I said in my original answer, this is a lot of manual work and also a maintenance nightmare like you said.
The powershell option is possible but also not very viable for the customer. You can't track your results in DevOps without looking into details for every run as they all have the same name, they are all the same test case for DevOps and just edited by the script.
I stopped looking for another solution, it looks like there is no better way to do this but if anybody else has a suggestion it could help someone else. Thanks all!
You can, but it's maintenance nightmare. If I change the test (record a new step) and I have 50 derived test cases, I need to update 50 parameter files with my test data again. It works, but it's not practical beyond a handful of derived test cases IMO
I'd say there are 2 practical solutions:
Would be interested in other options
You can use the derived test case, the recording is the same (means all the steps are the same) but with different parameter file.
test case 1: credit card, 30 daysm US-001, ABC1
test case 2: credit card, 30 daysm US-001, ABC2
and so on.
I don't have RSAT with me to provide screen shot, but this should help if I understand your requirement correctly.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,228 Super User 2024 Season 2
Martin Dráb 230,056 Most Valuable Professional
nmaenpaa 101,156