-
Notifications
You must be signed in to change notification settings - Fork 0
Milestone 2: Personal Contribution Page (Ali Alperen Sönmez)
AliAlperenSonmez edited this page May 12, 2023
·
2 revisions
- Name: Ali Alperen Sönmez
- Group: B2
Contribution | Related Issue(s) & Wiki Page(s) |
---|---|
Conducted a research about API's and found a usefull API for the practice app. | #74 |
- Name: Exchange Rates
- Route: https://api.exchangerate.host/convert
- Description: Given parameters, returns a json about corresponding exchange rate.
- Name: REQRES
- Route: https://reqres.in/api/users/
- Description: Given parameters, returns a json about a list of fake users.
- Name: GetExchangeRate
- Route: localhost:8000/api/exchange_rate_collect
- Description: Gives an exchange rate instance to the user by taking a json from the third party API.
- Name: POSTExchangeRate
- Route: localhost:8000/api/exchange_rate_new
- Description: This function is used to take an exchange rate from the user and put it to the database.
- Name: ClearExchangeRates
- Route: localhost:8000/api/exchange_rate_clear
- Description: Deletes all the exchange rate instances from the database.
- Name: GetData
- Route: localhost:8000/api/user-1_collect
- Description: Gives a fake user profile to the user by taking a json from the third party API.
- Name: POSTUser
- Route: localhost:8000/api/user-1_new
- Description: This function is used to take a fake user profile from the user and put it to the database.
- Name: ClearUsers
- Route: localhost:8000/api/user-1_clearall
- Description: Deletes all the fake user instances from the database.
- Test 1:
Checking whether the exchange rate object is created.
- Test 2:
Checking whether we can get a response with given parameters.
- Test 3:
Checking whether the post functionality works properly.
- Test 4:
Checking whether we can create an exchange rate by using third party API.
- Test 5:
Checking whether the clearall functionality works properly.
- Test 1:
Checking whether the user profile object is created.
- Test 2:
Checking whether we can get a response with given parameters.
- Test 3:
Checking whether the post functionality works properly.
- Test 4:
Checking whether we can create an exchange rate by using third party API.
- Test 5:
Checking whether the clearall functionality works properly.
- One of the biggest challenges in this project was learning and implementing a new framework, Django.
- Debugging and troubleshooting were also significant challenges throughout the development process.
- Time management was another challenge, but it was manageable with effective planning and prioritization.
- Additionally, ensuring code quality and maintainability was a continuous challenge that required ongoing attention and effort.
- Meeting 1 - 03/03/2023
- Meeting 2 - 09/03/2023
- Meeting 3 - 10/03/2023
- Meeting 4 - 16/03/2023
- Meeting 5 - 18/03/2023
- Meeting 6 - 23/03/2023
- Meeting 7 - 25/03/2023
- Meeting 8 - 30/03/2023
- Meeting 9 - 01/04/2023
- Meeting 10 - 06/04/2023
- Meeting 11 - 08/04/2023
- Meeting 12 - 27/04/2023
- Meeting 13 - 29/04/2023
- Meeting 14 - 04/05/2023
- Meeting 15 - 10/05/2023