===========================================================
.___ __ __
_________________ __ __ __| _/|__|/ |_
/ ___\_` __ \__ \ | | \/ __ | | \\_ __\
/ /_/ > | \// __ \| | / /_/ | | || |
\___ /|__| (____ /____/\____ | |__||__|
/_____/ \/ \/
grep rough audit - static analysis tool
v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
ruby-aruba-1.0.3/CHANGELOG.md-760-* Remove latency introduced in the 0.2.8 release ([#42], [msassak])
ruby-aruba-1.0.3/CHANGELOG.md:761:* New stepdef `Then /^the stdout should contain:$/ do |partial_output|` ([aslakhellesoy])
ruby-aruba-1.0.3/CHANGELOG.md-762-* Quotes (") and newline (\n) in step arguments no longer need to be backslash-escaped. ([aslakhellesoy])
##############################################
ruby-aruba-1.0.3/CHANGELOG.md-780- for a process to complete. Default: 1 second. ([aslakhellesoy])
ruby-aruba-1.0.3/CHANGELOG.md:781:* Fixed small bug in `/^the stdout should contain exactly:$/` ([aslakhellesoy])
ruby-aruba-1.0.3/CHANGELOG.md-782-
##############################################
ruby-aruba-1.0.3/CHANGELOG.md-866-
ruby-aruba-1.0.3/CHANGELOG.md:867:* `When /^I successfully run "(.*)"$/` now prints the combined output if exit
ruby-aruba-1.0.3/CHANGELOG.md-868- status is not 0. ([aslakhellesoy])
##############################################
ruby-aruba-1.0.3/features/03_testing_frameworks/cucumber/steps/command/check_output_of_command.feature-551- When I set the environment variable "ARUBA_TEST_VAR" to "first"
ruby-aruba-1.0.3/features/03_testing_frameworks/cucumber/steps/command/check_output_of_command.feature:552: And I run `bash -c 'printf $ARUBA_TEST_VAR'`
ruby-aruba-1.0.3/features/03_testing_frameworks/cucumber/steps/command/check_output_of_command.feature-553- Then the output from "bash -c 'printf $ARUBA_TEST_VAR'" should contain "first"
ruby-aruba-1.0.3/features/03_testing_frameworks/cucumber/steps/command/check_output_of_command.feature-554- When I set the environment variable "ARUBA_TEST_VAR" to "second"
ruby-aruba-1.0.3/features/03_testing_frameworks/cucumber/steps/command/check_output_of_command.feature:555: And I run `bash -c 'printf $ARUBA_TEST_VAR'`
ruby-aruba-1.0.3/features/03_testing_frameworks/cucumber/steps/command/check_output_of_command.feature-556- Then the output from "bash -c 'printf $ARUBA_TEST_VAR'" should contain "second"
##############################################
ruby-aruba-1.0.3/features/03_testing_frameworks/cucumber/steps/command/run_command_in_process.feature-219- to access IO from within your script. Unfortunately this does not work with
ruby-aruba-1.0.3/features/03_testing_frameworks/cucumber/steps/command/run_command_in_process.feature:220: the `:in_process`-command launcher. You need to use `$stderr`, `$stdout`
ruby-aruba-1.0.3/features/03_testing_frameworks/cucumber/steps/command/run_command_in_process.feature:221: and `$stdin` instead.
ruby-aruba-1.0.3/features/03_testing_frameworks/cucumber/steps/command/run_command_in_process.feature-222-
##############################################
ruby-aruba-1.0.3/debian/debian/03_testing_frameworks/cucumber/steps/command/check_output_of_command.feature-551- When I set the environment variable "ARUBA_TEST_VAR" to "first"
ruby-aruba-1.0.3/debian/debian/03_testing_frameworks/cucumber/steps/command/check_output_of_command.feature:552: And I run `bash -c 'printf $ARUBA_TEST_VAR'`
ruby-aruba-1.0.3/debian/debian/03_testing_frameworks/cucumber/steps/command/check_output_of_command.feature-553- Then the output from "bash -c 'printf $ARUBA_TEST_VAR'" should contain "first"
ruby-aruba-1.0.3/debian/debian/03_testing_frameworks/cucumber/steps/command/check_output_of_command.feature-554- When I set the environment variable "ARUBA_TEST_VAR" to "second"
ruby-aruba-1.0.3/debian/debian/03_testing_frameworks/cucumber/steps/command/check_output_of_command.feature:555: And I run `bash -c 'printf $ARUBA_TEST_VAR'`
ruby-aruba-1.0.3/debian/debian/03_testing_frameworks/cucumber/steps/command/check_output_of_command.feature-556- Then the output from "bash -c 'printf $ARUBA_TEST_VAR'" should contain "second"
##############################################
ruby-aruba-1.0.3/debian/debian/03_testing_frameworks/cucumber/steps/command/run_command_in_process.feature-219- to access IO from within your script. Unfortunately this does not work with
ruby-aruba-1.0.3/debian/debian/03_testing_frameworks/cucumber/steps/command/run_command_in_process.feature:220: the `:in_process`-command launcher. You need to use `$stderr`, `$stdout`
ruby-aruba-1.0.3/debian/debian/03_testing_frameworks/cucumber/steps/command/run_command_in_process.feature:221: and `$stdin` instead.
ruby-aruba-1.0.3/debian/debian/03_testing_frameworks/cucumber/steps/command/run_command_in_process.feature-222-