Makers Airport Challenge
=================
______
_\____\___
= = ==(____MA____)
\_____\___________________,-~~~~~~~`-.._
/ o o o o o o o o o o o o o o o o |\_
`~-.__ __..----..__ )
`---~~\___________/------------`````
= ===(_________)
Task
Use the TDD process to complete this challenge
My approach:
I'm using a project we worked on in pairs this week (the Boris Bikes challenge) as my framework for the Airport Challenge.
I spent most of Saturday redoing aforementioned challenge on my own, to make sure that I fully grasp the steps, thinking process, methods and syntax we used.
My Goals:
- Correctly follow the TDD process
- Create separate files for every class, module and test suite
- Achieve above 95% test coverage
- Learn about rubocop
- Finish the project
- If I don't complete this challenge on time, then I'll (hopefully) still be able to say that I know what I'm supposed to do and how to do it, even if it takes me a bit too long at the moment
Breakdown:
We have a request from a client to write the software to control the flow of planes at an airport. The planes can land and take off provided that the weather is sunny. Occasionally it may be stormy, in which case no planes can land or take off. Here are the user stories that we worked out in collaboration with the client:
As an air traffic controller
So I can get passengers to a destination
I want to instruct a plane to land at an airport
1st user story domain model:
| object | method |
|---|---|
| plane | instruct |
| land | |
| airport |
As an air traffic controller
So I can get passengers on the way to their destination
I want to instruct a plane to take off from an airport and confirm that it is no longer in the airport
2nd user story domain model:
| object | method |
|---|---|
| plane | take off |
| airport | left (confirm that plane is gone) |
As an air traffic controller
To ensure safety
I want to prevent takeoff when weather is stormy
3rd user story domain model:
| object | method |
|---|---|
| plane | grounded |
| storm |
As an air traffic controller
To ensure safety
I want to prevent landing when weather is stormy
4th user story domain model
| object | method |
|---|---|
| plane | prevent_landing |
| storm |
As an air traffic controller
To ensure safety
I want to prevent landing when the airport is full
5th user story domain model
| object | method |
|---|---|
| plane | prevent_landing |
| airport | full |
As the system designer
So that the software can be used for many different airports
I would like a default airport capacity that can be overridden as appropriate
6th user story domain model
| object | method |
|---|---|
| default-capacity | override |
Your task is to test drive the creation of a set of classes/modules to satisfy all the above user stories. You will need to use a random number generator to set the weather (it is normally sunny but on rare occasions it may be stormy). In your tests, you'll need to use a stub to override random weather to ensure consistent test behaviour.
Your code should defend against edge cases such as inconsistent states of the system ensuring that planes can only take off from airports they are in; planes that are already flying cannot takes off and/or be in an airport; planes that are landed cannot land again and must be in an airport, etc.
For overriding random weather behaviour, please read the documentation to learn how to use test doubles: https://www.relishapp.com/rspec/rspec-mocks/docs . There’s an example of using a test double to test a die that’s relevant to testing random weather in the test.
Please create separate files for every class, module and test suite.
In code review we'll be hoping to see:
- All tests passing
- High Test coverage (>95% is good)
- The code is elegant: every class has a clear responsibility, methods are short etc.
Reviewers will potentially be using this code review rubric. Referring to this rubric in advance will make the challenge somewhat easier. You should be the judge of how much challenge you want this weekend.
BONUS
- Write an RSpec feature test that lands and takes off a number of planes
Note that is a practice 'tech test' of the kinds that employers use to screen developer applicants. More detailed submission requirements/guidelines are in CONTRIBUTING.md
Finally, don’t overcomplicate things. This task isn’t as hard as it may seem at first.
-
Submit a pull request early. There are various checks that happen automatically when you send a pull request. Fix these issues if you can. Green is good.
-
Finally, please submit a pull request before Monday at 9am with your solution or partial solution. However much or little amount of code you wrote please please please submit a pull request before Monday at 9am.