This task helps us assess your basic understanding of how to manually test a web application and your ability to document what you observe. You will be testing the Risevest Web App (https://staging.rise-for-web-v2.pages.dev) and reporting your findings.
You are required to test the following 5 user flows. For each flow:
Describe the steps you took.
State the expected result at each step.
Note the actual result you got when testing.
Mark the test as Passed or Failed.
If any issues are found, describe the issue clearly.
- Login
-
Try logging in using valid credentials (we will provide test credentials).
-
Try logging in using invalid credentials.
-
What error message is shown?
- View Wallet
-
Navigate to the wallet/dashboard screen.
-
Is your wallet balance displayed?
-
Is it in the right format (e.g., β¦1,000.00)?
- Show/Hide Wallet Balance
-
Click on the eye icon or toggle to hide the balance.
-
Click again to show the balance.
-
Did the visibility change each time?
- View Investment Plans
-
Navigate to the Plans or Investments section.
-
Are any investment plans listed?
-
Are the plan details (name, amount, type) correct and readable?
- Create a New Plan
-
Start the process of creating a new investment plan.
-
Fill in details like amount and investment type.
-
Submit the form.
-
Is the new plan shown after saving?
-
Use a Google Doc, Notion page, or spreadsheet to write your results.
-
Include screenshots for any steps where something didnβt work as expected.
-
Bonus if you can suggest how to improve the app based on your experience using it.
3 days from the day you receive your test credentials.
If you have any experience in automation testing, feel free to write a simple test script (in any language you know) that tests at least the login page.
-
Clarity: Are your test steps and results easy to understand?
-
Thoroughness: Did you test all the listed flows?
-
Attention to Detail: Did you notice any issues or inconsistencies?
-
Communication: Are your reports well-written and free of typos?
This is not a pass/fail test. We are simply looking to understand how you approach testing and documentation. Show us how you think!
Good luck π―