Error Handling

Currently if the test user account in the config file is wrong or if RDS is already registered as an OAuth application to the test account, the test fails and doesn't show any messages which can explain the error.

Code Correction

The module.exports in this line:3 exports the whole variable and the value of the exported variable is being treated as an object here line:7. This is causing some problems in the test so export the variable as an object.

https://www.npmjs.com/package/expect-puppeteer

Why do we need it

Writing integration test is very hard, especially when you are testing a Single Page Applications. Data are loaded asynchronously and it is difficult to know exactly when an element will be displayed in the page.

Puppeteer API is great, but it is low level and not designed for integration testing.

This API is designed for integration testing:

• It will wait for element before running an action
• It adds additional feature like matching an element using text

Refactor tests for RDS homepage

• Write E2E tests for the index page (/ route)

Please make sure when you write tests run website-status code locally with API Mocking enabled

          can we move this to top as in the other file

Originally posted by @heyrandhir in #31 (comment)

Make sure the test doesn't break. check it once with yarn test.

Sign-up Workflow:

• GitHub Auth step (only once) via self call. If this step is not successful, then ask for login by redirecting to the basic signup page. If successful, then check for incomplete user details and redirect to the page where it can fill the details.
• With Submit, /user/details will send a patch call which contains all the details along with the userid.
• Then the Join section check whether user has been logged in or not . It asks to fill other details by prefilling the first and last name.
• This is a 4 page flow and in the 4th page we see the preview with Submit Button. On submit it sends a put request.
• In the backend there is a model known as applicants that checks all the user details and is only accessible by the super user.
• Finally it will land up on a page with a link which is a unique user and we get a button to get back to the home page.

The sign up tests are failing due to some bugs in the code.

The setup is done in multiple Pr's
#23 -> Installing Vitest
#24 -> Removing Jest
#25 -> Using Vitest

testflow after clicking join button

• logged in user -> join-page
• not logged in -> join-page -> alert -> redirect to signin (join-button.test.js)
• incomplete details - redirect back to home page

• Update all the npm packages to the recent version.
• Ensure everything is running fine