comment on

I have a script which uses several input files, creates some temps and outputs others. It is tested via Test::Script and file content/creation is tracked via Test:Directory and Test::File.

After adding a new feature, making sure the unit tests are passing, the script tests are failing. I attempt to debug by running the test file as perl -d:pdbtk t/path/to/test.t but cannot dive into the script itself.

It looks like the line executing the script from Tests::Script is the following:

(${$opt->{stdout}}, ${$opt->{stderr}}) = capture { system(@$cmd) };
[download]

but there is no way of 'stepping into' the execution.

I tried setting breakpoing inside the script, when entering the file, with $DB::single = 1 but no success.

I tried adding debug flag to the script_runs arguments, but it takes no effect.

edit: formatting

In reply to Test::Script debug execution via scripts_run by dpopchev

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


laziness, impatience, and hubris
	PerlMonks