LanX has asked for the wisdom of the Perl Monks concerning the following question:
I want to use Test::More's is_deeply() and probably other tests inside a web application, and am concerned about output and other side effects of the testing framework.
Is it possible to control the testing framework without destabilizing the app?
I'm aware about Data::Compare and Test::Deep::NoTest but would rather prefer not adding more dependencies.
TIA! :)
Cheers Rolf
(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)
Wikisyntax for the Monastery
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Controlling output and side effects from Test::More
by tobyink (Canon) on Jul 19, 2023 at 09:49 UTC | |
|
Re: Controlling output and side effects from Test::More (solved)
by LanX (Saint) on Jul 19, 2023 at 15:10 UTC |