…ts", that also generates an executable file on Windows
…se quotes more beautifully.
…lass. The refactored behaviors: 1. Take a blob of text, produce a list of runnable Step instances. 2. Run each of a list of steps. These will help with running steps inline from a step definition.
…ajtack/lettuce into ajtack-add_whitespace_between_scenarios
…r to look at.
…output now includes a full diff of the changes.
This fixes the raised in #52 where the unit tests would not pass if run in the same process and after functional tests were run (the default way that nosetests run thems). This commit fixes that. The registries are cleared and only the desired steps are defined. The issue at hand is the global `STEP_REGISTRY`, while a good idea, it was in an invalid state because of the way nosetests loads, then runs code. All test modules were being loaded into memory and the various steps were being defined inside tests.unit.test_step_runner. Once the tests started running, the tests in tests.functional.test_runner with `prepare_std*` setup methods were blowing away the steps that were stored in the `STEP_REGISTRY`. *NOTE*: This still wouldn't be thread safe (so far as I know) if you were to try to run all of the test methods in parallel you'd end up with each one of them trying to kill and setup the correct environment. There are ways to fix that, but they add additional complexity for something that's not widely done inside the Python community (yet, at least).