13 Commits

Author SHA1 Message Date
Mitchell Hashimoto
7eafb5fc1f Acceptance test that we can't add boxes with the same name 2012-01-10 18:45:38 -08:00
Mitchell Hashimoto
4e547becab Tests passing for GH-602 2011-12-25 09:57:20 -08:00
Mitchell Hashimoto
fc9bda08cd Failing test for port collision on resume [GH-602] 2011-12-25 09:29:22 -08:00
Mitchell Hashimoto
a8f5ed1863 Require vagrant environments for some commands. 2011-12-18 13:26:15 -08:00
Mitchell Hashimoto
f9653bf8d2 Some suspend tests 2011-11-24 16:15:45 -07:00
Mitchell Hashimoto
1ed1650fb6 vagrant halt acceptance tests 2011-11-22 19:34:25 -08:00
Mitchell Hashimoto
5d684b9001 Reload the configuration for all VMs after downloading a box. Fixes GH-564 2011-11-21 22:39:12 -08:00
Mitchell Hashimoto
bac87f2478 Complete the test (still failing) 2011-11-21 22:09:51 -08:00
Mitchell Hashimoto
d71a78eacf Failing acceptance test for GH-564 2011-11-21 21:55:03 -08:00
Mitchell Hashimoto
3a18119774 Fix failing destroy test for requiring a VM 2011-11-20 13:39:54 -08:00
Mitchell Hashimoto
38d28800be Destroy acceptance tests 2011-11-20 13:37:01 -08:00
Mitchell Hashimoto
4443a323e5 Create the output matcher, switch to RSpec style matchers 2011-11-08 23:03:15 -08:00
Mitchell Hashimoto
87bc6ec63f RSpec is coming in for acceptance tests. More details follow...
RSpec was chosen to be used for acceptance tests for many reasons:

* The tests are actually much cleaner now. It is clearer to see what
  is being tested, and what is being used for setup.
* Matcher transition will be coming soon. This will really clean up
  a lot of the "assert" boilerplate all over. There was a lot of repetition
  in this area.
* Shared examples will help greatly for testing common error cases
  for many commands.
* The test runner for RSpec is simply much better. Being able to specify
  the exact test to run by line, for example, is a great help.
2011-11-06 23:47:23 -08:00