-
Notifications
You must be signed in to change notification settings - Fork 104
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #277 from deeseeker/test/scenario-for-manual-testing
test: Create scenario for manual testing
- Loading branch information
Showing
1 changed file
with
169 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,169 @@ | ||
### **Scenario 1: Connect to Different Wallets (Argent X, Bravos)** | ||
|
||
**Steps:** | ||
|
||
1. Install Argent X and Bravos extensions in your browser. | ||
2. Open the application following the guide in the Read.me file. | ||
3. Click on the "Connect Wallet" button. | ||
4. Select "Argent X" from the wallet options. | ||
5. Confirm the connection in the Argent X wallet. | ||
6. Disconnect the wallet. | ||
7. Repeat steps 3–5 for the Bravos wallet. | ||
|
||
**Expected Results:** | ||
|
||
- The app connects successfully to both wallets. | ||
- Wallet addresses are displayed after connection. | ||
|
||
**Bugs:** | ||
|
||
- Error: Network Error occurs in the TVL and Users sections when a wallet connection persists from the last login; disconnecting and reconnecting the wallet resolves the issue. | ||
|
||
### **Scenario 2: Open Position with Different Wallets** | ||
|
||
**Steps:** | ||
|
||
1. Ensure your wallet has some STRK tokens and ETH. | ||
2. Connect to the app using the Argent X wallet. | ||
3. Navigate to the "Launch App" section. | ||
4. Select "token" from the wallet options. | ||
5. Choose “multiplier.” | ||
6. Input the desired token amount. | ||
7. Click "Submit" and confirm the transaction in the wallet. | ||
8. Navigate to the “Position” section in the dashboard. | ||
9. Repeat steps 2–8 using the Bravos wallet. | ||
|
||
**Expected Results:** | ||
|
||
- The position is successfully created and appears in the dashboard for both wallets. | ||
- A success or failure modal for the transaction is displayed. | ||
- Transaction details appear in the dashboard. | ||
|
||
**Bugs:** | ||
|
||
1. **Internal Server Error (500)**: Occurs when creating a position. | ||
2. Failure message text does not appear. | ||
3. Open positions do not show in the dashboard. | ||
|
||
### **Scenario 3: Close Position with Different Wallets** | ||
|
||
**Steps:** | ||
|
||
1. Connect to the app using the Argent X wallet. | ||
2. Navigate to the "Positions" section in the dashboard. | ||
3. Select an open position and click "Close Position." | ||
4. Confirm the transaction in the wallet. | ||
5. Repeat steps 1–4 using the Bravos wallet. | ||
|
||
**Expected Results:** | ||
|
||
- Positions are successfully closed for both wallets. | ||
- Balances update correctly. | ||
|
||
**Bugs:** | ||
|
||
1. Closed positions do not show in the dashboard. | ||
|
||
### **Scenario 4: Open Position with Different Tokens** | ||
|
||
**Steps:** | ||
|
||
1. Follow the steps in Scenario 1 to connect the wallet. | ||
2. Repeat the steps in Scenario 2 to create a position. | ||
3. For each attempt, select a different token: | ||
|
||
- First: Select ETH. | ||
- Second: Select STRK. | ||
- Third: Select DAI. | ||
- Fourth: Select USDC. | ||
|
||
**Expected Results:** | ||
|
||
- Positions are successfully created for all tokens and appear in the dashboard. | ||
- A success or failure modal for each transaction is displayed. | ||
- Transaction details are visible in the dashboard. | ||
|
||
**Bugs:** | ||
|
||
1. **Internal Server Error (500)**: Occurs when creating a position. | ||
2. Failure message text does not appear. | ||
3. Open positions do not show in the dashboard. | ||
|
||
### **Scenario 5: Validate Footer Links Functionality** | ||
|
||
#### **Steps to Reproduce** | ||
|
||
1. **Connect Wallet**: | ||
|
||
- Use the Argent X wallet to connect to the application. | ||
|
||
2. **Navigate to Footer**: | ||
|
||
- Scroll down to the **Footer** section on the home page. | ||
|
||
3. **Click All Links**: | ||
|
||
- Individually click each link in the footer. | ||
|
||
4. **Verify Resources**: | ||
|
||
- Confirm that each link redirects to the intended resource or page. | ||
|
||
#### **Expected Results** | ||
|
||
- All links in the footer should: | ||
|
||
- Be functional (not broken). | ||
- Redirect to the correct resources as intended. | ||
|
||
#### **Bugs Identified** | ||
|
||
1. **GitHub Link:** | ||
|
||
- Redirects to the general [github.com](https://github.com) instead of the Spotnet repository. | ||
|
||
2. **Overview Link:** | ||
|
||
- Does not navigate to the Overview resource as expected. | ||
|
||
3. **Terms and Conditions Link:** | ||
|
||
- Fails to point to the Terms and Conditions resource. | ||
|
||
4. **DeFi Link:** | ||
|
||
- Not linked to any resource (broken or inactive). | ||
|
||
5. **Twitter Link:** | ||
|
||
- Does not redirect to the associated Twitter profile. | ||
|
||
#### **Scenario 6: Validate Application Display on Mobile Devices** | ||
|
||
#### **Steps to Reproduce** | ||
|
||
1. **Test Device and Viewports**: | ||
|
||
- Devices: iPhone SE, iPhone 12 Pro, Samsung Galaxy S8 | ||
- Viewports: 320px, 375px | ||
|
||
2. **Navigate to the Application**: | ||
|
||
- Open the application on the specified devices or adjust the viewport size in the browser's developer tools. | ||
|
||
3. **Inspect Layout and Responsiveness**: | ||
|
||
- Verify that the application displays properly and adapts to the screen size. | ||
- Check for layout issues, alignment problems, content overflow, and UI functionality. | ||
|
||
#### **Expected Results** | ||
|
||
- The application should display consistently and adapt to all screen sizes tested. | ||
- Layout should be responsive without content overlap, overflow, or misaligned UI elements. | ||
- Interactive elements should remain accessible and functional. | ||
|
||
#### **Bugs Identified** | ||
|
||
1. Content overflows horizontally on several pages. | ||
2. Page sections have inconsistent padding, leading to uneven alignment. | ||
3. Content at the form section of the page is clipped. |