head 1.1; access; symbols pkgsrc-2023Q4:1.1.0.60 pkgsrc-2023Q4-base:1.1 pkgsrc-2023Q3:1.1.0.58 pkgsrc-2023Q3-base:1.1 pkgsrc-2023Q2:1.1.0.56 pkgsrc-2023Q2-base:1.1 pkgsrc-2023Q1:1.1.0.54 pkgsrc-2023Q1-base:1.1 pkgsrc-2022Q4:1.1.0.52 pkgsrc-2022Q4-base:1.1 pkgsrc-2022Q3:1.1.0.50 pkgsrc-2022Q3-base:1.1 pkgsrc-2022Q2:1.1.0.48 pkgsrc-2022Q2-base:1.1 pkgsrc-2022Q1:1.1.0.46 pkgsrc-2022Q1-base:1.1 pkgsrc-2021Q4:1.1.0.44 pkgsrc-2021Q4-base:1.1 pkgsrc-2021Q3:1.1.0.42 pkgsrc-2021Q3-base:1.1 pkgsrc-2021Q2:1.1.0.40 pkgsrc-2021Q2-base:1.1 pkgsrc-2021Q1:1.1.0.38 pkgsrc-2021Q1-base:1.1 pkgsrc-2020Q4:1.1.0.36 pkgsrc-2020Q4-base:1.1 pkgsrc-2020Q3:1.1.0.34 pkgsrc-2020Q3-base:1.1 pkgsrc-2020Q2:1.1.0.30 pkgsrc-2020Q2-base:1.1 pkgsrc-2020Q1:1.1.0.10 pkgsrc-2020Q1-base:1.1 pkgsrc-2019Q4:1.1.0.32 pkgsrc-2019Q4-base:1.1 pkgsrc-2019Q3:1.1.0.28 pkgsrc-2019Q3-base:1.1 pkgsrc-2019Q2:1.1.0.26 pkgsrc-2019Q2-base:1.1 pkgsrc-2019Q1:1.1.0.24 pkgsrc-2019Q1-base:1.1 pkgsrc-2018Q4:1.1.0.22 pkgsrc-2018Q4-base:1.1 pkgsrc-2018Q3:1.1.0.20 pkgsrc-2018Q3-base:1.1 pkgsrc-2018Q2:1.1.0.18 pkgsrc-2018Q2-base:1.1 pkgsrc-2018Q1:1.1.0.16 pkgsrc-2018Q1-base:1.1 pkgsrc-2017Q4:1.1.0.14 pkgsrc-2017Q4-base:1.1 pkgsrc-2017Q3:1.1.0.12 pkgsrc-2017Q3-base:1.1 pkgsrc-2017Q2:1.1.0.8 pkgsrc-2017Q2-base:1.1 pkgsrc-2017Q1:1.1.0.6 pkgsrc-2017Q1-base:1.1 pkgsrc-2016Q4:1.1.0.4 pkgsrc-2016Q4-base:1.1 pkgsrc-2016Q3:1.1.0.2 pkgsrc-2016Q3-base:1.1; locks; strict; comment @# @; 1.1 date 2016.09.19.09.00.50; author mef; state Exp; branches; next ; commitid mpoQJ8MJX18HwSmz; desc @@ 1.1 log @Import p5-Test-Toolbox-0.4 as devel/p5-Test-Toolbox. Test::Toolbox provides (as you might guess) tools for automated testing. Test::Toolbox is much like some other testing modules, such as Test::More and Test::Simple. Test::Toolbox provides a different flavor of tests which may or may not actually be to your preference. The tools in Test::Toolbox have a standard format. Commands start with (the command (of course), followed by the test name. Then there is usually the value being tested, or values being compared, then other options. So, for example, this command checks compares two values: rtcomp 'test name', $val, $other_val; In some cases it's preferable to flip the logic of the test, so that, for example, two values should not be the same. In that case, you can add the should option: rtcomp 'test name', $val, $other_val, should=>0; All test commands require a test name as the first param. @ text @Test::Toolbox provides (as you might guess) tools for automated testing. Test::Toolbox is much like some other testing modules, such as Test::More and Test::Simple. Test::Toolbox provides a different flavor of tests which may or may not actually be to your preference. The tools in Test::Toolbox have a standard format. Commands start with (the command (of course), followed by the test name. Then there is usually the value being tested, or values being compared, then other options. So, for example, this command checks compares two values: rtcomp 'test name', $val, $other_val; In some cases it's preferable to flip the logic of the test, so that, for example, two values should not be the same. In that case, you can add the should option: rtcomp 'test name', $val, $other_val, should=>0; All test commands require a test name as the first param. @