https://github.com/angristan/solid-library-kata
https://github.com/angristan/solid-library-kata
Last synced: 7 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/angristan/solid-library-kata
- Owner: angristan
- Created: 2021-02-08T15:12:39.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2021-02-09T02:09:38.000Z (over 4 years ago)
- Last Synced: 2025-03-15T15:45:02.843Z (7 months ago)
- Language: Go
- Homepage:
- Size: 23.4 KB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Solid Library Kata
We decided to try an experiment in a new Field: software for Libraries.
In order to build this proof of concept, we interviewed a few potential clients.
This is the summary of the most important features to start with:
* For the books we have in our library, we identify them by their title and by
the author's name.
* Only the librarian can add and reference a new book in the library
* Guests can see the content of the library but they cannot borrow books.
* Members can borrow books but they can only have 3 books at the same time.
They can only keep the books for a maximum period of time of 4 weeks _(ex: They can
borrow 2 books, return 1 after 1 week, take 2 another books, return the first
after 3 more weeks and the 2 new books after 4 weeks)_
* a user only needs an unique login to be identified (you don't need names, passwords
and so on for this version)
Technical notes:
- There is no bi-directional user interaction but your app needs to be scriptable.
- you can choose the persistence of your choice, but the simpler the better
- your application needs to be testable and must be tested
Design notes:
- the application should be very simple in terms of user interface (ie: an app console is good enough for this test) but
internally well designed.
- ask questions to check if there is hidden rules
- define your main use cases and find 2-3 exemples to illust
---
```
Usage:
-action string
action to do