![\"Adi](\"http:\/\/blog.adrianbolboaca.ro\/wp-content\/uploads\/2020\/01\/adi-emily-1024x576.png\")
<\/a><\/p>\n<\/p>\n
Problem<\/strong>:<\/p>\nSince lifts are everywhere and they contain software, how easy would it be to write a basic one? Let\u2019s TDD a lift, starting with simple behaviors and working toward complex ones. Assume good input from calling code and concentrate on the main flow.<\/p>\n
Lift features:<\/p>\n
\n- a lift moves between a number of floors.<\/li>\n
- a lift has a panel of buttons passengers can press to\u00a0request<\/em>\u00a0floors.<\/li>\n
- people can call the lift from other floors. A\u00a0call<\/em>\u00a0has both a floor and a desired direction.<\/li>\n
- a lift has doors which may be open or closed.<\/li>\n<\/ul>\n
In this repository, that much is already implemented. The following features are not yet implemented:<\/p>\n
\n- a lift fulfills a\u00a0request<\/em>\u00a0when it moves to the requested floor and opens the doors.<\/li>\n
- a lift fulfills a\u00a0call<\/em>\u00a0when it moves to the correct floor, is about to go in the called direction, and opens the doors.<\/li>\n
- a lift can only move between floors if the doors are closed.<\/li>\n<\/ul>\n
Lifts do not respond immediately or do everything at once. To simplify handling time in this exercise, the provided LiftSystem class has a ‘tick’ method. Every time you call it, the lift system should simulate a unit of time passing, and update its state according to what changes occurred during that time period. Lifts can move between floors or open their doors for example.<\/p>\n
To simplify things, Lifts only accept new calls and requests when they are on a floor. (Then we don’t have to model what happens when they are between floors).<\/p>\n
You can find the code and the whole descripton here: https:\/\/github.com\/adi-bolb\/Lift-Kata\/tree\/pairing-with-emily<\/p>\n
Video<\/h2>\n
Check the video Approval Tests with Lift Kata and please come with your ideas and comments<\/p>\n