teacup-on-rockingchair / guard-cunit Goto Github PK

ERROR: Guard::Cunit failed to achieve its <run_on_change>, exception was:
ArgumentError: wrong number of arguments (1 for 0)
/usr/lib/ruby/gems/1.9.1/gems/guard-cunit-0.0.1/lib/guard/cunit.rb:24:in run_on_change' /usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard/runner.rb:90:inblock in run_supervised_task'
/usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard/runner.rb:88:in catch' /usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard/runner.rb:88:inrun_supervised_task'
/usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard/runner.rb:137:in block in run_first_task_found' /usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard/runner.rb:135:ineach'
/usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard/runner.rb:135:in run_first_task_found' /usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard/runner.rb:71:inblock in run_on_changes'
/usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard/runner.rb:161:in block (3 levels) in scoped_guards' /usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard/runner.rb:160:ineach'
/usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard/runner.rb:160:in block (2 levels) in scoped_guards' /usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard/runner.rb:159:incatch'
/usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard/runner.rb:159:in block in scoped_guards' /usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard/runner.rb:158:ineach'
/usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard/runner.rb:158:in scoped_guards' /usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard/runner.rb:63:inrun_on_changes'
/usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard.rb:110:in block (2 levels) in setup_listener' /usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard.rb:323:inblock in within_preserved_state'
internal:prelude:10:in synchronize' /usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard.rb:320:inwithin_preserved_state'
/usr/lib/ruby/gems/1.9.1/gems/guard-1.2.3/lib/guard.rb:109:in block in setup_listener' /usr/lib/ruby/gems/1.9.1/gems/listen-0.4.7/lib/listen/listener.rb:190:incall'
/usr/lib/ruby/gems/1.9.1/gems/listen-0.4.7/lib/listen/listener.rb:190:in on_change' /usr/lib/ruby/gems/1.9.1/gems/listen-0.4.7/lib/listen/listener.rb:199:inblock in initialize_adapter'
/usr/lib/ruby/gems/1.9.1/gems/listen-0.4.7/lib/listen/adapter.rb:162:in call' /usr/lib/ruby/gems/1.9.1/gems/listen-0.4.7/lib/listen/adapter.rb:162:inpoll_changed_dirs'
/usr/lib/ruby/gems/1.9.1/gems/listen-0.4.7/lib/listen/adapters/linux.rb:44:in `block in start'

Guard::Cunit has just been fired

fixed by commit 1f6e251

parser of cunit output does not handle suite initialization failure, in case programmer does not take care to report error exit code in that case.
The Cunit generally outputs following message:
WARNING - Suite initialization failed for ....
and in the summary one can see that we have suites that are not run. For example:

[#] Run Summary: Type Total Ran Passed Failed Inactive
[#] suites 3 2 n/a 1 0
[#] tests 26 24 24 0 0
[#] asserts 185 185 185 0 n/a

On some systemd the stderr output is not seen when guard is started, also spawning the tasks via the popen, by default givesme only stdout. That is ok with my dflt configuration issuing 'make 2>&1' but I would consider that not so elegant solution so will submit a patch to always merge in popen call stderr and stdout output

rake failed for ruby.19.3 look at http://travis-ci.org/#!/strandjata/guard-cunit/jobs/2532591 build 7 jobs 7.3 and 7.7

used wrong symbol for displaying passed test

rake failed on ruby 1.8.7 for reference travis build 7 http://travis-ci.org/#!/strandjata/guard-cunit/jobs/2532591 jobs 7.1,7.4and 7.6

here how the rspec execution looked like on MAC (I needed to type 'quit' on each test that called guard.run):

testmacs-Mac:guard-cunit testmac$ rspec -f d

Guard::Cunit::CunitParser
should generate a UI summary and full output from given text input
failure summary should be maximum a 3 row output
should be able to init with no output and later trigger process

Guard::Cunit
should inherit Guard class
Run guard
should run build
should run build on changes

should set libpath for executbles with current project directory by default

[1] guard(main)> quit
should set libpath to predefined lib directory when user has specified such in the Guardfile[1] guard(main)> quit

[1] guard(main)> quit
[1] guard(main)> quit
should run cunit test define in the Guardfile
[1] guard(main)> quit
should run predefined build command
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
[1] guard(main)> quit
should run predefined clean command
Handle exit codes
[1] guard(main)> quit
should report failure on build failed
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
[1] guard(main)> quit
should report failure on test failed
Displaying notifications
[1] guard(main)> quit
should display failure if build fails
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
[1] guard(main)> quit
should display failure if test fails
[1] guard(main)> quit
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
should display pending if test is absent
should display success if build and test succeeded

Finished in 10.24 seconds
17 examples, 0 failures
testmacs-Mac:guard-cunit testmac$

it is quite annoying that even when the build fails tests are executed