Added Logout user scenario

[Lemeri123]

This pull request introduces the UserLogoutScenario class, which is designed to simulate the user logout process in the OpenMRS performance testing suite. The scenario ensures that the logout functionality is contributing to the overall robustness and reliability of the system.

Additionally:
Added a logoutRequest method so that the UserLogoutScenario can correctly reference the logoutRequest method.

[Lemeri123]

@jayasanka-sack please look through this and let me know if am on the right track

[Bawanthathilan]

@jayasanka-sack please look through this and let me know if am on the right track

Hi @Lemeri123 , Your PR is basically adding a logout user scenario. But why create a new scenario when we already have existing ones? Scenarios represent real-world actions performed by personas in the system—like a doctor going to the hospital, logging into the system, opening a chart page, and starting a visit.

However, your change introduces a new scenario where the doctor goes to the hospital just to trigger a system logout, which doesn’t quite fit. Also, logout itself isn’t typically considered part of a scenario.

[jayasanka-sack]

Thanks for your PR @Lemeri123! As @Bawanthathilan mentioned, a scenario in load testing represents a sequence of real-world user interactions rather than a single action. Users don’t typically go to a system just to log out, so this doesn’t align with how scenarios are structured.

We intentionally did not include logout in our existing scenarios because, in real-world usage, most users don’t explicitly log out from the system.

I’ll go ahead and close this PR, but we appreciate the effort! ❤️
Feel free to contribute to other areas where improvements are needed. Thanks again!

[Lemeri123]

Ohhh @Bawanthathilan, @jayasanka-sack thanks for the guidance

[Lemeri123]

Ohhhh by the way @jayasanka-sack, @Bawanthathilan can an appointment booking scenario be a valid scenario?? or the existing scenarios are all we need?????

[jayasanka-sack]

That’s a valid scenario. Could you please draft a Google Doc with the steps and all the API calls involved? Once we verify everything, you can start implementing it.