To add a collaborator to this project you will need to use the Relish gem to add the collaborator via a terminal command. Soon you'll be able to also add collaborators here!
More about adding a collaboratorrbld
As a CLI user
I want to interfere with system via main script called rbld
- Scenarios
-
- rbld unknown_command fails with error
- rbld help unknown_command fails with error
- there is no log by default
- log is enabled by RBLD_LOG_LEVEL environment variable
- various log levels supported
- log is redirected to file by RBLD_LOG_FILE environment variable
- stack backtrace is not printed on incorrect command line
- stack backtrace of exceptions is logged as FATAL
- stack backtrace is not printed on signal
- stack backtrace of signal is logged as FATAL
- rbld unknown_command fails with error
-
- Given
-
I run
rbld unknown_command - Then
-
it should fail with:
ERROR: Unknown command: unknown_command
- rbld help unknown_command fails with error
-
- Given
-
I run
rbld help unknown_command - Then
-
it should fail with:
ERROR: Unknown command: unknown_command
- there is no log by default
-
- Given
-
I run
rbld - Then
- the output should not contain "INFO: ARGV:"
- log is enabled by RBLD_LOG_LEVEL environment variable
-
- Given
-
I set the environment variables to:
variable value RBLD_LOG_LEVEL debug - When
-
I run
rbld - Then
- the output should contain "INFO: ARGV:"
- various log levels supported
-
- Given
-
I set the environment variables to:
variable value RBLD_LOG_LEVEL level - When
-
I run
rbld - Then
- the output should or should not contain "INFO: ARGV:"
Examples: level should or should not debug should info should warn should not error should not fatal should not unknown should not - log is redirected to file by RBLD_LOG_FILE environment variable
-
- Given
-
I set the environment variables to:
variable value RBLD_LOG_LEVEL debug RBLD_LOG_FILE rbld.log - When
-
I run
rbld - Then
- the output should not contain "INFO: ARGV:"
- And
- a file "rbld.log" should contain "INFO: ARGV:"
- stack backtrace is not printed on incorrect command line
-
- When
-
I run
rbld run --wrong-opt - Then
- the output should not contain "<main>"
- stack backtrace of exceptions is logged as FATAL
-
- Given
-
I set the environment variables to:
variable value RBLD_LOG_LEVEL fatal - When
-
I run
rbld run --wrong-opt - Then
- the output should match /FATAL.+rbld.+<main>/
- stack backtrace is not printed on signal
-
- When
- I send signal "INT" to rbld application
- Then
- the output should not contain "<main>"
- And
- the output should contain "ERROR: Command execution was terminated."
- stack backtrace of signal is logged as FATAL
-
- Given
-
I set the environment variables to:
variable value RBLD_LOG_LEVEL fatal - When
- I send signal "INT" to rbld application
- Then
- the output should match /FATAL.+rbld.+<main>/
Last published almost 5 years ago by Rebuild.