dpopchev has asked for the wisdom of the Perl Monks concerning the following question:
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:
but there is no way of 'stepping into' the execution.(${$opt->{stdout}}, ${$opt->{stderr}}) = capture { system(@$cmd) };
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
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Test::Script debug execution via scripts_run
by dpopchev (Novice) on Apr 22, 2021 at 04:51 UTC | |
Re: Test::Script debug execution via scripts_run
by Perlbotics (Archbishop) on Apr 21, 2021 at 17:55 UTC | |
Re: Test::Script debug execution via scripts_run
by Anonymous Monk on Apr 21, 2021 at 15:38 UTC |