Is there a way to organize the threads to avoid the logout ,when your running in multiple threads for the same feature

[Kannan0893]

Hello ,

we have around 2000+ automated UI test cases, when we tried to run with multiple threads, then we are seeing logout failures in same feature if we trigger with multiple thread then we are seeing logout failures , we tried with scenario level is there a way to avoid this logout failure when we are running in multiple treads ? is there way to organize the threads to avoid this logout failures ?

if we try with feature level ,then we are getting report as feature level count . ex. we have 2000 test cases with 10 features . then the feature level report giving count as 10 .. Is there a way to change the report alone for the total test case count even if we execute with feature level ??

please suggest us some solution for this issue

Thanks, Kannan P

[prashant-ramcharan]

Hello,

Using CourgetteRunLevel.SCENARIO means you have to write loosely coupled tests where each scenario / test can pass independently of any other scenario / test. This is best practice and should be followed whenever possible.

As your tests depend on application state (the user must be logged in / out etc), using CourgetteRunLevel.SCENARIO will never work, so using CourgetteRunLevel.FEATURE would be your only option as you figured out.

I will have to have a think about how to be best represent this in the Courgette html report as using CourgetteRunLevel.FEATURE means I have limited access to scenario level statistics (re-run info etc.)

[Kannan0893]

Thanks for the quick response @prashant-ramcharan .. please let me know if you found any work around or changes will support our use case

Thanks, Kannan P

[Kannan0893]

Hi @prashant-ramcharan ..did u get a chance to check on this ?

[prashant-ramcharan]

Hi @Kannan0893 , unfortunately I've not had much time to progress on this.

[prashant-ramcharan]

@Kannan0893 this change is now released in Courgette 6.9.1

[Kannan0893]

Thanks a lot @prashant-ramcharan ... let me execute the test cases and get back to you if we have any concerns