-
Antonio Terceiro authored
- make each sample log/output pair an individual test case - use a test assertion for comparing output instead of custom code - switch from test-unit to minitest, as that gives way better failure output. For example: > $ sed -i -e /^Reason:/d test/dest/chef_12.10.24-1_unstable.output > $ rake > [...] > # Running: > > .......................................................................F > > Failure: > LogsTest#test_chef_12_10_24_1_unstable_log [/home/terceiro/src/debian/collab-qa-tools/test/tc_logs.rb:31]: > --- expected > +++ actual > @@ -1,5 +1,4 @@ > "chef 12.10.24-1 Failed 126.825449994 > -Reason: RUBY_TEST_FAILED > > 1-line summary: > ERROR: Test \"ruby2.3\" failed.
Antonio Terceiro authored- make each sample log/output pair an individual test case - use a test assertion for comparing output instead of custom code - switch from test-unit to minitest, as that gives way better failure output. For example: > $ sed -i -e /^Reason:/d test/dest/chef_12.10.24-1_unstable.output > $ rake > [...] > # Running: > > .......................................................................F > > Failure: > LogsTest#test_chef_12_10_24_1_unstable_log [/home/terceiro/src/debian/collab-qa-tools/test/tc_logs.rb:31]: > --- expected > +++ actual > @@ -1,5 +1,4 @@ > "chef 12.10.24-1 Failed 126.825449994 > -Reason: RUBY_TEST_FAILED > > 1-line summary: > ERROR: Test \"ruby2.3\" failed.
This project manages its dependencies using RubyGems.
Learn more