amigoscode/cohort-2-d

cohort-2-d's Issues

Setup oders - some fixes: Controller, Service, Repo, Dao

Category: create dto, model, service, controller classes

Add tests to github workflow

Fix tests for: book, category, and author. Pair programming

User Setup files structure - create user - get user by id - get users

Modify book controller a second time

Search books - fix

Book: create dto, model, service, controller classes

Test app running correctly - simple controller

Admin / Customer: Search books

User Story Title: A bookstore admin or customer can search the store to find books they are interested in.

Scenario 1: Successful search - book matches

Given a search query that will results in matches
When I make a GET request to the API endpoint with the search query
Then the system should respond with a 200 status code the system should display a list of books matching query

Scenario 2: Unsuccessful search - no book matches

Given a search query which will result in no matches
When I make a GET request to the API endpoint with the search query
Then the system should respond with a 200 status code the system should display an error message saying no books have been found.

Bootstrap empty spring project with basic dependencies

Fix @Qualifier and @NotNull validqtion constraint

Remove test application.yml

Admin: Add new books

User Story Title: A bookstore admin can add new books to the store in line with trends in the bestseller charts and new releases.

Scenario 1: Successfully add a book to the store

Given all necessary and correct information to add a new book
When I make a POST request to the API endpoint with a book’s information
Then the system should respond with a 201 status code

Scenario 2: Attempting to add a book with duplicate information

Given all necessary information to add a new book but duplicate information given e.g. title
When I make a POST request to the API endpoint with the user information to add a new user
Then the system should respond with a 400 status code and an error message indicating that the book already exists.

Scenario 3: Attempting to add a book with incorrect / incomplete information

Given all incorrect information to add a new book e.g. incorrect data type / missing title
When I make a POST request to the API endpoint with the user information to add a new book
Then the system should respond with a 400 status code and an error message indicating that the information supplied is incorrect

Add global exception handling

Fix address test - Nelson review

Modify book controller again !

Address Setup

Fix: Refactor book, category & author

Refactor so that add transactions are made in separate requests

Setup Testcontainers

Author: Finish get, update and delete

Setup and configure Database

Setup Security: Authentication - Autorization

Mofify Book Controller

Clean up and adapt created project

Setup flyway structure

Modify Book Controller

Admin: Delete books

User Story Title: A bookstore admin can delete books if they are not selling.

Scenario 1: Successfully deleting an existing book

Given a valid book ID.
When I make a DELETE request to the API endpoint with the book’s ID to delete the book.
Then the system should respond with a 200 status code and a message indicating that the book has been deleted successfully.

Scenario 2: Attempting to delete a non-existing book

Given an invalid book ID.
When I make a DELETE request to the API endpoint with the book’s ID to delete the book.
Then the system should respond with a 404 status code and an error message indicating that the book does not exist.

Modify book controller a second time

Category: Finish get, update and delete

Setup Unit and Integration tests

Admin: Update and edit books

User Story Title: A bookstore admin can edit and update books in the store books so that stock information is up-to-date and correct.

Scenario 1: Successfully update a book in the store

Given a valid book ID and book information
When I make a PUT request to the API endpoint with the book’s ID and updated book information
Then the system should respond with a 200 status code and a message indicating that the book has been updated successfully

Scenario 2: Attempting to update a non-existing book

Given an invalid book ID
When I make a PUT request to the API endpoint with the book’s ID and updated book information
Then the system should respond with a 404 status code and an error message indicating that the book does not exist

Scenario 3: Attempting to update a book entry without providing updated information

Given a valid book ID
When I make a PUT request to the API endpoint with the book’s ID without providing updated book information
Then the system should respond with a 400 status code and an error message indicating that updated information must be provided for the update.