- Clone/Download the source code.
- Go to root directory
/savingsgoal - Execute following command from command line
mvn spring-boot:run.That should both build and run the app. - Point 3 should enable URL http://localhost:8080, and the operation should be available at
/round-up - Set the Authorization header token and start using the round up service.
- I have also attached the swagger file (api-docs.yaml) in
/resourcesfor reference.
Make sure the customer (Used in APi call) has a valid token , account/s , transaction feed and Savings Goal setup.
- Perform a
Getcall onhttp://localhost:8080/round-upafter building and running the application. Pass the bearer access token from any rest client. - The app will then find the account/s associated with the token, next the app will find all the feeds available to account/s round them up and save it to the respective account goal. A response list containing details of top up will be sent back to the caller.
- If there are any missing details in point 2 for cases like customer doesn't have an account or there is no feed available for the requested time frame (A week, as asked in test) or there are no saving goals, an error will be thrown to indicate exact problem (more details in StarlingAdapterImpl class comments )
1. JDK 15
2. SpringBoot 2.4.0
3. Junit5 BDD Mockito
4. Jacoco
5. Lombok
6. Springdoc-openapi
- A user can have more than one account e.g. Savings , current and EUR/GBP etc.
- In case of multiple goals per account the first one would be taken, as there might be ambiguity in picking up goal and there is no customer interaction.
- Multiple calls to roundup api with same token where no change in account feed has happened will have no effect on saving goal account. A logic in place to exclude goal savings transfers (Direction OUT) from being calculated as transaction feeds and round up in case multiple invocations are made subsequently. As they are not spending but a txn towards goal.
- Go to root directory
/savingsgoal - execute
mvn test