Implement the Cypress e2e test to test the login flow of krini

[anuragxxd]

Is your feature request related to a problem? Please describe.
As the CI pipeline runs certain tests on the Krini before deploying it to the production. Checking the login flow will be a good test to be written in case OIDC auth is broken by any code changes.

Describe the solution you'd like
We can write the cypress e2e test that tests for the login flow before deploying the application to production.

Describe alternatives you've considered
--NA--

Additional context
A test can be written in the file ./cypress/e2e/spec.cy.js under the test auth -> user can login. This test is already integrated into the CI pipeline & this can be tested by running npm run cypress:open.

[ghost]

Hi @git-anurag-hub, can you please assign this issue to me?

[uniqueg]

Hi @tanya17-05, I think @Sanyam2000-dot is already working on this, but I'm not sure. @git-anurag-hub: can you please write some more issues and make sure both @Sanyam2000-dot and @tanya17-05 have issues to work on? Thanks 🙏🏻

[anuragxxd]

Yeah sure @uniqueg. @Sanyam2000-dot can you confirm if you are working on this?

[Sanyam2000-dot]

Hello Anurag, Yes I'm working on this issue. Thanks!

[ghost]

Ok @Sanyam2000-dot, let me know if you need any kind of help.

[Sanyam2000-dot]

Ok @Sanyam2000-dot, let me know if you need any kind of help.

Thanks @tanya17-05 . I'll ket you know.

[anuragxxd]

Hey @Sanyam2000-dot are you working on this?

[Sanyam2000-dot]

Hello @git-anurag-hub, I have started this but have not completed it due to some health issues in the family. It will be good if you can assign it to Tanya so I can guide her forward.

[anuragxxd]

Np @Sanyam2000-dot , TC!

[SohamRatnaparkhi]

Hi,
Can I work on this issue? I have some experience in writing Cyprus tests.
My approach would be, using cyprus:

• clicking the login button on home screen
• clicking on Login with LS username
• entering test username and password
• clicking on login button
• searching for Run workflow button to confirm login was successful.

Code snippet in spec.cy.js file that I wrote in my forked repo to solve this issue would be -

Here, we will require some test username and password to be stored in .env which can be used for testing.
I am open for suggestions to my approach.

[anuragxxd]

Sure @SohamRatnaparkhi, go ahead with it!

[SohamRatnaparkhi]

Okay, Thank you @git-anurag-hub
What should be the test_password and test_username in this case?

[anuragxxd]

Hey @SohamRatnaparkhi, you can right now try out with yours & configure the same in the .env.test!