ariessa-deriv / syntrade-backend Goto Github PK

Describe the bug
When query for user(user_id: 1), it responded with details for user(user_id: 4)

To Reproduce
Steps to reproduce the behavior:

1. Go to http://localhost:4000
2. Query
   {
   user(user_id: 1) {
   user_id
   email
   password
   wallet_balance
   date_joined
   }
   }

Expected behavior
Details for user(user_id: 1) should be returned

Screenshots

Desktop (please complete the following information):

• OS: Linux
• Browser: chrome
• Version: 105

Describe the bug
The back-end server returns "Failed to get all users"

To Reproduce
Steps to reproduce the behavior:

1. Go to http://localhost:4000
2. Query
   { users { user_id email password wallet_balance date_joined } }
3. See the error

Expected behavior
The response should return all user details

Screenshots

Desktop (please complete the following information):

• OS: Linux
• Browser: Google Chrome
• Version: 105

Describe the bug
When query for trade(trade_id: 1), it responded with details for trade(trade_id: 3)

To Reproduce
Steps to reproduce the behavior:

1. Go to http://localhost:4000
2. Query
   {
   trade(trade_id: 1) {
   trade_id
   user_id
   synthetic_type
   currency
   trade_time
   trade_type
   trade_result
   current_wallet_balance
   }
   }

Expected behavior
Details for trade(trade_id: 1) should be returned

Screenshots

Desktop (please complete the following information):

• OS: Linux
• Browser: chrome
• Version: 105

Describe the bug
When querying for user_id: 1, the respond got is from user_id: 3 instead. Noticed that the respond gives the last data from user data every single time.

To Reproduce
Steps to reproduce the behavior:

1. Go to http://localhost:4000
2. Query
   { user(user_id: 1) { user_id email password wallet_balance date_joined } }
3. See the user_id response

Expected behavior
It should return the specific user_id details

Screenshots

Desktop (please complete the following information):

• OS: Linux
• Browser: chrome
• Version: 105

Describe the bug
It shows an error code in the response body indicating that the trade buying is unsuccessful

To Reproduce
Steps to reproduce the behavior:

1. Open Postman
2. Insert this query

 mutation {
    createTrade(syntheticType: "volatility_10_rise", wagerAmount: 198, optionType: "put", ticks: 4)
  }

Expected behavior
It should not show an error message

Screenshots

Desktop (please complete the following information):

• OS: Linux
• Browser: Google Chrome
• Version: 105

Describe the bug
The login endpoint cannot read user details

To Reproduce
Steps to reproduce the behavior:

1. Go to http://localhost:4000/
2. Insert this query

mutation { login(email: "[email protected]", password: "Abcd123!") { email password } }
3. See the error

Expected behavior
The endpoint should be able to read the user details

Screenshots

Desktop (please complete the following information):

• OS: Linux
• Browser: Google Chrome
• Version: 105

Tool

• Tested using GraphQL and Postman

Describe the bug
The current data type for current_wallet_balance is string

To Reproduce
Steps to reproduce the behavior:

1. Go to http://localhost:4000
2. Query
   {
   trades {
   trade_id
   user_id
   synthetic_type
   currency
   trade_time
   trade_type
   trade_result
   current_wallet_balance
   }
   }

Expected behavior
The data type for current_wallet_balance should be float

Screenshots

Desktop (please complete the following information):

• OS: Linux
• Browser: Chrome
• Version: 105

Describe the bug
Does not return all details from trade (give null instead)

To Reproduce
Steps to reproduce the behavior:

1. Go to http://localhost:4000
2. Query
   { trade(trade_id: 1) { trade_id user_id synthetic_type currency trade_time trade_type trade_result current_wallet_balance } }
3. See the respond

Expected behavior
Return all details from trade

Screenshots

Desktop (please complete the following information):

• OS: Linux
• Browser: Chrome
• Version: 105

Describe the bug
The information returned are null

To Reproduce
Steps to reproduce the behavior:

1. Go to http://localhost:4000
2. Query
   mutation { login(email: "[email protected]", password: "Abc4123!") { email, password } }
3. See the details returned are null

Expected behavior
Back-end server should return JWT token

Screenshots

Desktop (please complete the following information):

• OS: Linux
• Browser: Google Chrome
• Version: 105

Describe the bug
It shows an error code in the response body indicating that the trade buying is unsuccessful

To Reproduce
Steps to reproduce the behavior:

1. Open Postman
2. Insert this query

 mutation {
    createTrade(syntheticType: "volatility_25_matches", wagerAmount: 198, optionType: "call", ticks: 7, lastDigitPrediction: 2)
  }

Expected behavior
It should not show an error message

Screenshots

Desktop (please complete the following information):

• OS: Linux
• Browser: Google Chrome
• Version: 105