would trigger failure when the test is later fixed!here' first runc:\pp \system\testerpython tester py start testermon feb : : in :\users\mark\stuff\books\ \pp \dev\examples\pp \system\tester generating\outputs\test-basic-args out generating\outputs\test-basic-stdout out generating\outputs\test-basic-streams out generating\outputs\test-basic-this out error statustest-errors-runtime py error streamtest-errors-runtime py \errors\test-errors-runtime err error statustest-errors-syntax py error streamtest-errors-syntax py \errors\test-errors-syntax err error statustest-status-bad py generating\outputs\test-status-good out finishedmon feb : : tests were run tests failed to run each scriptthe tester configures any preset command-line arguments providedpipes in fetched canned input (if any)and captures the script' standard output and error streamsalong with its exit status code when ran this examplethere were test scriptsalong with variety of inputs and outputs since the directory and file naming structures are the key to this examplehere is listing of the test directory used--the scripts directory is primarybecause that' where tests to be run are collectedc:\pp \system\testerdir / args errors inputs outputs scripts tester py xxold :\pp \system\testerdir / scripts test-basic-args py test-basic-stdout py test-basic-streams py test-basic-this py test-errors-runtime py test-errors-syntax py test-status-bad py test-status-good py the other subdirectories contain any required inputs and any generated outputs associated with scripts to be testedc:\pp \system\testerdir / args test-basic-args args test-status-good args complete system programs