search for: autofeature

Hi! And now for the second part of the subject of my previous mails :) $ cat cucumber.yml default: . autotest: -v . autotest-all: -v -f progress . $ cucumber -i . -f progress PP Pending Scenarios: 1) enlightenment (meditation) $ AUTOFEATURE=true autospec # bug! prompt returns immediately, ZenTest gem not a dependency? a warning that autotest was not found would be nice. $ sudo gem install ZenTest Successfully installed ZenTest-3.11.0 1 gem installed Installing ri documentation for ZenTest-3.11.0... Installing RDoc documentation fo...

OS=CentOS-5.2 Ruby=1.8.6 Rails=2.2.1_RC Gems all up to date I have been experimenting with autotest and I have a few questions. 1. given export AUTOFEATURES=TRUE if ./test exists (with tests) then these tests are run and the features are not. Is this intended behaviour? 2. given require ''autotest/redgreen'' in .autotest if /test tests are run then all I get colourized is a line of ''======'' but if /test is removed a...

...cation, and I install autotest (and autotest -v does not work, so I can''t see which version number I actually get), and the gem system claims I have version 4.1.3. And I run autotest in the project folder, and it says: $ autotest (Not running features. To run features in autotest, set AUTOFEATURE=true.) /usr/bin/ruby1.8 -I.:lib:test -rubygems -e "%w[test/unit test/test_helper.rb].each { |f| require f }" | unit_diff -u Loaded suite -e Started Finished in 0.000437 seconds. 0 tests, 0 assertions, 0 failures, 0 errors Note the system did not even run the whole test batch, first. A...

When running autotest with AUTOFEATURE=true, all of my specs and features run fine. However, if I have a feature containing a scenario that fails, autotest lists that feature, but then returns "0 scenarios", and then runs all of the features again. Any idea why this might be? Best, Tom -- Posted via http://www.ruby-forum.c...