/usr/bin/manager

Controlling Test Order
  --ginkgo.seed [int] (default: randomly generated by Ginkgo)
    The seed used to randomize the spec suite.
  --ginkgo.randomize-all
    If set, ginkgo will randomize all specs together.  By default, ginkgo only
    randomizes the top level Describe, Context and When containers.

Controlling Test Parallelism
These are set by the Ginkgo CLI, do not set them manually via go test.
Use ginkgo -p or ginkgo -procs=N instead.
  --ginkgo.parallel.process [int] (default: 1)
    This worker process's (one-indexed) process number.  For running specs in
    parallel.
  --ginkgo.parallel.total [int] (default: 1)
    The total number of worker processes.  For running specs in parallel.
  --ginkgo.parallel.host [string] (default: set by Ginkgo CLI)
    The address for the server that will synchronize the processes.

Filtering Tests
  --ginkgo.label-filter [expression]
    If set, ginkgo will only run specs with labels that match the label-filter.
    The passed-in expression can include boolean operations (!, &&, ||, ','),
    groupings via '()', and regular expressions '/regexp/'.  e.g. '(cat || dog)
    && !fruit'
  --ginkgo.sem-ver-filter [version]
    If set, ginkgo will only run specs with semantic version constraints that
    are satisfied by the provided version. e.g. '2.1.0'
  --ginkgo.focus [string]
    If set, ginkgo will only run specs that match this regular expression. Can
    be specified multiple times, values are ORed.
  --ginkgo.skip [string]
    If set, ginkgo will only run specs that do not match this regular
    expression. Can be specified multiple times, values are ORed.
  --ginkgo.focus-file [file (regexp) | file:line | file:lineA-lineB | file:line,line,line]
    If set, ginkgo will only run specs in matching files. Can be specified
    multiple times, values are ORed.
  --ginkgo.skip-file [file (regexp) | file:line | file:lineA-lineB | file:line,line,line]
    If set, ginkgo will skip specs in matching files. Can be specified multiple
    times, values are ORed.

Failure Handling
  --ginkgo.fail-on-pending
    If set, ginkgo will mark the test suite as failed if any specs are pending.
  --ginkgo.fail-fast
    If set, ginkgo will stop running a test suite after a failure occurs.
  --ginkgo.flake-attempts [int] (default: 0 - failed tests are not retried)
    Make up to this many attempts to run each spec. If any of the attempts
    succeed, the suite will not be failed.
  --ginkgo.fail-on-empty
    If set, ginkgo will mark the test suite as failed if no specs are run.
  --ginkgo.sleep-on-failure [duration] (default: 0 - disabled)
    If set, ginkgo will pause for this duration after a spec fails - before its
    teardown (AfterEach/JustAfterEach/DeferCleanup) runs - so you can inspect
    the live system. Press ^C to end the pause early and proceed to cleanup.
    Serial only: cannot be combined with -p/--procs.

Controlling Output Formatting
  --ginkgo.no-color
    If set, suppress color output in default reporter.  You can also set the
    environment variable GINKGO_NO_COLOR=TRUE
  --ginkgo.v
    If set, emits more output including GinkgoWriter contents.
  --ginkgo.vv
    If set, emits with maximal verbosity - includes skipped and pending tests.
  --ginkgo.succinct
    If set, default reporter prints out a very succinct report
  --ginkgo.trace
    If set, default reporter prints out the full stack trace when a failure
    occurs
  --ginkgo.show-node-events
    If set, default reporter prints node > Enter and < Exit events when specs
    fail
  --ginkgo.github-output
    If set, default reporter prints easier to manage output in Github Actions.
  --ginkgo.silence-skips
    If set, default reporter will not print out skipped tests.
  --ginkgo.force-newlines
    If set, default reporter will ensure a newline appears after each test.
  --ginkgo.fd
    If set, emits RSpec-style 'format documentation' output instead of Ginkgo's
    default output.  --fd is exclusive: it overrides -p/-procs and
    -randomize-all, forcing specs to run serially in declaration order, since
    fd's hierarchical output can't be rendered sensibly when specs are
    parallelized or randomized.
  --ginkgo.json-report [filename.json]
    If set, Ginkgo will generate a JSON-formatted test report at the specified
    location.
  --ginkgo.gojson-report [filename.json]
    If set, Ginkgo will generate a Go JSON-formatted test report at the
    specified location.
  --ginkgo.junit-report [filename.xml]
    If set, Ginkgo will generate a conformant junit test report in the specified
    file.
  --ginkgo.teamcity-report [filename]
    If set, Ginkgo will generate a Teamcity-formatted test report at the
    specified location.

Debugging Tests
In addition to these flags, Ginkgo supports a few debugging environment
variables.  To change the parallel server protocol set GINKGO_PARALLEL_PROTOCOL
to HTTP.  To avoid pruning callstacks set GINKGO_PRUNE_STACK to FALSE.
  --ginkgo.dry-run
    If set, ginkgo will walk the test hierarchy without actually running
    anything.  Best paired with -v.
  --ginkgo.poll-progress-after [duration] (default: 0)
    Emit node progress reports periodically if node hasn't completed after this
    duration.
  --ginkgo.poll-progress-interval [duration] (default: 10s)
    The rate at which to emit node progress reports after poll-progress-after
    has elapsed.
  --ginkgo.source-root [string]
    The location to look for source code when generating progress reports.  You
    can pass multiple --source-root flags.
  --ginkgo.timeout [duration] (default: 1h)
    Test suite fails if it does not complete within the specified timeout.
  --ginkgo.grace-period [duration] (default: 30s)
    When interrupted, Ginkgo will wait for GracePeriod for the current running
    node to exit before moving on to the next one.
  --ginkgo.output-interceptor-mode [dup, swap, or none]
    If set, ginkgo will use the specified output interception strategy when
    running in parallel.  Defaults to dup on unix and swap on windows.

Go test flags
  -config string
    	The controller will load its initial configuration from this file. Omit this flag to use the default configuration values.
  -feature-gates string
    	A set of key=value pairs that describe feature gates for alpha/experimental features.
  -kubeconfig string
    	Paths to a kubeconfig. Only required if out-of-cluster.
  -zap-devel
    	Development Mode defaults(encoder=consoleEncoder,logLevel=Debug,stackTraceLevel=Warn). Production Mode defaults(encoder=jsonEncoder,logLevel=Info,stackTraceLevel=Error)
  -zap-encoder value
    	Zap log encoding (one of 'json' or 'console')
  -zap-log-level value
    	Zap Level to configure the verbosity of logging. Can be one of 'debug', 'info', 'error', 'panic' or any integer value > 0 which corresponds to custom debug levels of increasing verbosity
  -zap-stacktrace-level value
    	Zap Level at and above which stacktraces are captured (one of 'info', 'error', 'panic').
  -zap-time-encoding value
    	Zap time encoding (one of 'epoch', 'millis', 'nano', 'iso8601', 'rfc3339' or 'rfc3339nano'). Defaults to 'epoch'.