我正在修复一个大型测试脚本(> 1000 行),该脚本使用一些实用方法(也> 1000 行)对各种初始数据设置执行重复测试。这有助于整合代码。但是,当测试失败时,它会报告实用程序方法内部的行号,从而很难跟踪哪个测试失败了。
是否可以配置Test::Most为在测试失败时提供堆栈跟踪而不是仅提供单个行号?
#!/usr/bin/env perl
use strict;
use warnings;
use autodie;
use Test::Most tests => 3;
ok(1, 'first test');
note "The following includes a failed test, but a stack trace would be more helpful";
helper_sub_with_test(); # Line 13
ok(1, 'third test');
sub helper_sub_with_test {
ok(0, "second test"); # Line 17
}
Run Code Online (Sandbox Code Playgroud)
输出:
$ perl scratch.pl
1..3
ok 1 - first test
# The following includes a failed test, but a stack trace would be more helpful
not ok 2 - second test
# Failed test 'second test'
# at scratch.pl line 17.
ok 3 - third test
# Looks like you failed 1 test of 3.
Run Code Online (Sandbox Code Playgroud)
正如您所看到的,如果失败的测试同时报告第 17 行和第 13 行,那么当多次调用实用程序方法时,将会很有帮助。
我不相信 Test::More 基础设施提供了如此强大的功能,但是您真的需要堆栈跟踪吗?只要您为测试提供描述性名称,仅报告第 13 行就足够了。
要报告第 13 行而不是第 17 行,只需将以下内容添加到您的子文件中:
local $Test::Builder::Level = $Test::Builder::Level + 1;
Run Code Online (Sandbox Code Playgroud)
更长的例子:
#!/usr/bin/env perl
use strict;
use warnings;
use autodie;
use Test::Most tests => 3;
ok(1, 'first test');
note "The following includes a failed test, but a stack trace would be more helpful";
helper_sub_with_test(); # Line 13
ok(1, 'third test');
sub helper_sub_with_test {
local $Test::Builder::Level = $Test::Builder::Level + 1;
ok(0, sprintf "second test (look at line %d)", __LINE__); # Line 18
}
Run Code Online (Sandbox Code Playgroud)