chiquito83 / cloudstorage Goto Github PK

Every time Selenium creates a new user, logs in, and then creates/delete/edits a note. But as per the requirement, we have to log in with the existing user and verify the workflow of note.

You have already created a user for testing the signupLoginAndLogout() test case. Use the same credentials to log in.

Please implement the same and provide us with the updated code.

💡 Every functionality is working great, just update the code to remove repetitive signup before performing any operation and directly login with existing registered credentials.
You can use the @order annotation to run all the test cases sequentially. This will ensure that the signup test case will always run before testing note functionality.
If you are using the org.junit.jupiter.api package for @order annotation and it above version 5.5, we have to add a type-level annotation @TestMethodOrder.

When the user clicks on the "Upload" button without selecting any file a "default empty file" is uploaded.

Only document-type files are downloaded into the local system. Other file types such as, .py, .pdf, .png opens up in a new browser window.

In the credential dashboard, the password should be displayed in an encrypted format.
Points to be considered:

In the credential dashboard, the password should be in an encrypted format.
While editing, in the form the pre-filled password should be in decrypted format.

One of the issues that need to be handled is mentioned above that for every operation a success message should be displayed. No success message logic is yet implemented.

Users can add duplicate values, this should be prohibited.

When a user tries to upload the same file multiple times a warning message should be displayed indicating, "File already exists". And no file should be uploaded.