Joonas Kuisma
Joonas Kuisma
Hi! Is the issue still occurring? To me, the command ``` pabot --testlevelsplit -v env:dev --outputdir test --name WebCommonLogin FunctionalTesting/Login.robot ``` and the attached screenshots don't quite match. With this...
Hi, and sorry to hear that your ordering file no longer works. Due to new features and bug fixes, I had to make some small changes in version 5.0.0. The...
Hi @MarvKler ! Did you manage to get that working?
Hi! I think that you should add --testlevelsplit if you want to run Test Cases in order (not suite level)
I believe that previously the ordering file was somewhat more flexible, but it caused issues in certain situations. After fixing those problems, the ordering file now requires a full path...
Hi! Have you tried checking if the issue also occurs with the latest version of Pabot?
Hi, I think pabot’s --argumentfileN could be the solution. For example: pabot --argumentfile1 person1.args --argumentfile2 person2.args. Then you just define the desired Robot run command-line parameters and variables inside the...
Hi @aradhana-g ! Could you kindly provide more information about the issue? For example, the version, environment, etc., as well as a more detailed description of the problem. As it...
Hi! This appears to be the same "connection refused" issue as in #546, so I’m closing this one. We can reopen it if needed — especially if someone can provide...
Hi @patrikwilliam ! Could this issue be closed, or do you still consider it urgent? #558 appears to have already been merged.