The cart sample includes a Vagrantfile, behat tests and plain old PHP objects (POPOs) that model the functionality of a basic shopping cart.

The cart sample uses Vagrant to provision and configure a Virtual Machine that satisfies all the dependencies for the code to work.

• VirtualBox 4.3.x. Download here: https://www.virtualbox.org/wiki/Downloads
  • Do not use VirtualBox 5.x.x. It is currently not compatible with Vagrant.
• Vagrant 1.7.x. Download here: http://www.vagrantup.com/downloads

• Make sure you have a working internet connection. The virtual machine will be downloading packages from the internet in order to configure itself.
• Download and install Virtualbox.
• Download and install Vagrant.
• Start the Vagrant box (VM) by typing: vagrant up
• During the startup process, the virtual machine will be provisioned with git, php and composer.

Note: We expect installation to take 15-30 minutes to setup. If for any reason it is taking longer, please feel free to reach out to us. We are happy to help.

After installation, ssh into the vagrant box and confirm the tests are working:

$ vagrant ssh
$ cd /vagrant
$ behat

The tests should complete without errors. The majority of the tests will be in a pending state.

Here is a high level overview of the important files in this project:

• features/cart.feature - the gherkin language that describes scenarios (tests cases) for the sample cart code.
• features/bootstrap/FeatureContext.php - the Behat file that parses the above cart.feature and executes tests.
• src/HauteLook/Cart.php - the sample cart class
• src/HauteLook/Product.php - the same product class

Vagrant will automatically sync any changes you make to these files from your host operating system, so feel free to use whatever editor your are most comfortable with to browse and edit them.

The first scenario has been written for you. Please implement as many of the remaining scenarios in `features/cart.feature' as you can within the next 60 minutes. We are judging you on the simplcity of your design and the correctness of the code. Make whatever changes you want to the scenario implementations and source code to accomplish that goal. Do not worry if you cannot finish all of them. Find a good stopping point and send us what you have. We are excited to see it! Zip up the entire directory and email it back to us.

Need help? Please reach out to us! We know computers can be tricky things and we are happy to assist you. Our contact details are in the email we sent you. We will get back to you as soon as we can.