arunsk12/akumar

Java Test

Your first task will be to fork this repo and follow the instructions below.

The sprint lasts up to 2 hours but you can complete it earlier if you wish. It ends once you issue your pull request from your fork back to our repository.

Please make commits as you go (> 1, < 100).

A boilerplate Spring Boot MVC application has been setup with Maven to get you started. However, you are completely free to delete it and start again with another framework (or no framework) if you would prefer. Just make sure you provide steps to build and run the application if you don't use Spring Boot.

Using spring boot we will test the application with mvn clean install and will then run the jar file:

java -jar target/java-test-0.1.0.jar

(With spring boot the jar will include the application server.)

The Story

"As an Consumer of the API, I would like to be able to add, retrieve, remove and update Cars in your application via a RESTFul API."

If the story needs to be broken down to fit into the sprint, please do so.

The Acceptance Criteria

• Priority order is:
  1. add
  2. retrieve
  3. remove
  4. update
• My Car has the following attributes:
  • Id*
  • Make
  • Model
  • Year of manufacture
  • Entry Date*
• We do not require persistent storage (in-memory is fine).

*generated by the application on entry

Subsequent stories you can bring into the sprint if you have time

1. "As a Developer, I want my code to be covered by unit tests so I know if a change has broken something"
2. "As a Developer, I want my code to be covered by integration tests so I know if a change has broken something"
3. "As a Consumer of the API, I would like any Cars I add through the API to be persisted between application reloads (persistent storage)"
4. "As a Consumer of the API, I would like Cars to be represented as two, separate, linked resources: Make (Id, Name, Entry Date) and Model (Id, Name, Year of Manufacture, MakeUri, Entry Date)"

Limitations

You can use whatever online resources you want (aside from copy-pasting large chunks of code, obviously).

You are encouraged to use any frameworks or libraries you feel comfortable with.