黄瓜错误被抑制（未完全显示）

2 回答

• 14

  使用 -b 标志运行应该会给你一个完整的回溯

  cucumber features/manage_users.feature -b
  

  编辑：

  此外，您可以使用 --backtrace 的完整表示法 . 如果您通过rake运行，请使用 --trace 标志运行

  要获得完整输出，可以使用 --format 标志 . 我通常使用 --format pretty 来逐行浏览 .

  来自 --help 输出 .

  -f, --format FORMAT              How to format features (Default: pretty). Available formats:
                                     debug       : For developing formatters - prints the calls made to the listeners.
                                     html        : Generates a nice looking HTML report.
                                     json        : Prints the feature as JSON
                                     json_pretty : Prints the feature as pretty JSON
                                     junit       : Generates a report similar to Ant+JUnit.
                                     pdf         : Generates a PDF report. You need to have the
                                                   prawn gem installed. Will pick up logo from
                                                   features/support/logo.png or
                                                   features/support/logo.jpg if present.
                                     pretty      : Prints the feature as is - in colours.
                                     progress    : Prints one character per scenario.
                                     rerun       : Prints failing files with line numbers.
                                     stepdefs    : Prints All step definitions with their locations. Same as
                                                   the usage formatter, except that steps are not printed.
                                     tag_cloud   : Prints a tag cloud of tag usage.
                                     usage       : Prints where step definitions are used.
                                                   The slowest step definitions (with duration) are
                                                   listed first. If --dry-run is used the duration
                                                   is not shown, and step definitions are sorted by
                                                   filename instead.
                                   Use --format rerun --out features.txt to write out failing
                                   features. You can rerun them with cucumber @rerun.txt.
                                   FORMAT can also be the fully qualified class name of
                                   your own custom formatter. If the class isn't loaded,
                                   Cucumber will attempt to require a file with a relative
                                   file name that is the underscore name of the class name.
                                   Example: --format Foo::BarZap -> Cucumber will look for
                                   foo/bar_zap.rb. You can place the file with this relative
                                   path underneath your features/support directory or anywhere
                                   on Ruby's LOAD_PATH, for example in a Ruby gem.
  

  回复于 2024-05-10T19:54:00+08:00
• 1

  如果您的应用程序是Rails应用程序，则可以将@ allow-rescue标记用于感兴趣的场景，然后rails test_log将包含有关应用程序中最初引发错误的位置的更多详细信息 .

  从命令行，您可以使用tail -n200 log / test_log.rb快速查看测试日志的结尾（调整行数以查看感兴趣的部分） .

  回复于 2024-05-10T19:54:00+08:00