Airport Challenge

A request from a client to write the software to control the flow of planes at an airport.

Getting started

Fork this repo
Clone to your local machine git clone git@github.com:CharlyMannion/airport_challenge.git
Run the command gem install bundle (if you don't have bundle already)
When the installation completes, run bundle
Run the command gem install bundle (if you don't have bundle already)
When the installation completes, run bundle

Running tests

rspec

How I approached the challenge

I followed a TDD approach to this challenge. My first step was to write a feature tests, and watch them fail. I would then use the feature test to help me write a unit test, and watch it fail. I would read the error messages the unit test generated to help me write the code I wanted. I ran rubocop regularly to help me improve my code. I repeated this process to grow the program and meet the requirements in the user stories. When I had satisfied all the user stories, I began to think about ways my code could be improved e.g. by guarding against edge cases. When I was happy with the program at a particular point, I attempted to refactor to follow principles such as DRY. I tried to ensure the principle of single responsibility was followed. I ensured I had a high test coverage. I made it my goal to use doubles and mocking in my tests to improve in this area.

What I would like to do to improve my program

I would like to refactor my code further i.e. use blocks to set up stubbing behaviour that is shared across a number of tests. I would like to include tests to make sure my program would work for multiple planes.

irb Transcript sample

Charlys-Air:airport_challenge charlymannion$ irb 2.5.0 :001 > require './docs/airport' => true 2.5.0 :002 > airport = Airport.new => #<Airport:0x00007fb227902b40 @stationed_planes=[], @capacity=10, @weather=#Weather:0x00007fb227902b18> 2.5.0 :003 > plane = Plane.new