tlevine/urchin
1
0
Fork 0
Code Issues 5 Pull Requests 1 Packages Projects Releases Wiki Activity

move tests out temporarily

Browse Source
This commit is contained in:
Thomas Levine 2016-02-28 18:24:14 +00:00
parent efab5cde8e
commit 287e54a4fe
86 changed files with 0 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

0
tests/- directories starting with a hypen.../Should work → tests.old/- directories starting with a hypen.../Should work
View File

0
tests/.die-on-fail/1 should run. → tests.old/.die-on-fail/1 should run.
View File

0
tests/.die-on-fail/2 should run. → tests.old/.die-on-fail/2 should run.
View File

0
tests/.die-on-fail/3 should not run. → tests.old/.die-on-fail/3 should not run.
View File

0
tests/.die-on-fail/4 should not run. → tests.old/.die-on-fail/4 should not run.
View File

0
tests/.example-test-suite/this should fail → tests.old/.example-test-suite/this should fail
View File

0
tests/.example-test-suite/this should pass → tests.old/.example-test-suite/this should pass
View File

0
tests/.gitignore → tests.old/.gitignore vendored
View File

0
tests/.print-arg-3 → tests.old/.print-arg-3
View File

0
tests/A nonempty CDPATH should not break urchin. → tests.old/A nonempty CDPATH should not break urchin.
View File

0
tests/Command-line help contents/The -f flag should be documented. → tests.old/Command-line help contents/The -f flag should be documented.
View File

0
tests/Command-line help contents/The -s option should be documented. → tests.old/Command-line help contents/The -s option should be documented.
View File

0
tests/Command-line help contents/Urchin should exit 0 if run with the -h flag. → tests.old/Command-line help contents/Urchin should exit 0 if run with the -h flag.
View File

0
tests/Command-line help contents/Urchin should exit 1 if help is displayed without being requested. → tests.old/Command-line help contents/Urchin should exit 1 if help is displayed without being requested.
View File

0
tests/Counts should be kept of successes and failures./.test-one/fail → tests.old/Counts should be kept of successes and failures./.test-one/fail
View File

0
tests/Counts should be kept of successes and failures./.test-one/pass → tests.old/Counts should be kept of successes and failures./.test-one/pass
View File

0
tests/Counts should be kept of successes and failures./.test/faila → tests.old/Counts should be kept of successes and failures./.test/faila
View File

0
tests/Counts should be kept of successes and failures./.test/failb → tests.old/Counts should be kept of successes and failures./.test/failb
View File

0
tests/Counts should be kept of successes and failures./.test/failc → tests.old/Counts should be kept of successes and failures./.test/failc
View File

0
tests/Counts should be kept of successes and failures./.test/passa → tests.old/Counts should be kept of successes and failures./.test/passa
View File

0
tests/Counts should be kept of successes and failures./.test/passb → tests.old/Counts should be kept of successes and failures./.test/passb
View File

0
tests/Counts should be kept of successes and failures./.test/passc → tests.old/Counts should be kept of successes and failures./.test/passc
View File

0
tests/Counts should be kept of successes and failures./.test/passd → tests.old/Counts should be kept of successes and failures./.test/passd
View File

0
tests/Counts should be kept of successes and failures./.test/passe → tests.old/Counts should be kept of successes and failures./.test/passe
View File

0
tests/Counts should be kept of successes and failures./.test/passf → tests.old/Counts should be kept of successes and failures./.test/passf
View File

0
tests/Counts should be kept of successes and failures./.test/passg → tests.old/Counts should be kept of successes and failures./.test/passg
View File

0
tests/Counts should be kept of successes and failures./Singular form is used for a single failure. → tests.old/Counts should be kept of successes and failures./Singular form is used for a single failure.
View File

0
tests/Counts should be kept of successes and failures./Singular form is used for a single pass. → tests.old/Counts should be kept of successes and failures./Singular form is used for a single pass.
View File

0
tests/Counts should be kept of successes and failures./There should be seven successes. → tests.old/Counts should be kept of successes and failures./There should be seven successes.
View File

0
tests/Counts should be kept of successes and failures./There should be three failures. → tests.old/Counts should be kept of successes and failures./There should be three failures.
View File

0
tests/Cross-shell test support/.test-TEST_SHELL-passed-through/$TEST_SHELL should be bash. → tests.old/Cross-shell test support/.test-TEST_SHELL-passed-through/$TEST_SHELL should be bash.
View File

0
tests/Cross-shell test support/.test-TEST_SHELL-undefined_or_empty/Invoking a command with $TEST_SHELL should work → tests.old/Cross-shell test support/.test-TEST_SHELL-undefined_or_empty/Invoking a command with $TEST_SHELL should work
View File

0
tests/Cross-shell test support/.test-run-by-specified-shell/With -s, a non-sh test script should be invoked directly. → tests.old/Cross-shell test support/.test-run-by-specified-shell/With -s, a non-sh test script should be invoked directly.
View File

0
tests/Cross-shell test support/.test-run-by-specified-shell/With -s, a sh test script should be invoked with the specified shell. → tests.old/Cross-shell test support/.test-run-by-specified-shell/With -s, a sh test script should be invoked with the specified shell.
View File

0
tests/Cross-shell test support/.test-run-by-specified-shell/With -s, a shebang-less test script should be invoked with the specified shell. → tests.old/Cross-shell test support/.test-run-by-specified-shell/With -s, a shebang-less test script should be invoked with the specified shell.
View File

0
tests/Cross-shell test support/.test-run-by-specified-shell/With -s, the TEST_SHELL environment variable should be set to the specified shell too. → tests.old/Cross-shell test support/.test-run-by-specified-shell/With -s, the TEST_SHELL environment variable should be set to the specified shell too.
View File

0
tests/Cross-shell test support/Environment variable TEST_SHELL should be passed through. → tests.old/Cross-shell test support/Environment variable TEST_SHELL should be passed through.
View File

0
tests/Cross-shell test support/Environment variable TEST_SHELL should default to sh if empty. → tests.old/Cross-shell test support/Environment variable TEST_SHELL should default to sh if empty.
View File

0
tests/Cross-shell test support/Environment variable TEST_SHELL should default to sh if unset. → tests.old/Cross-shell test support/Environment variable TEST_SHELL should default to sh if unset.
View File

0
tests/Cross-shell test support/The -s option should invoke tests with the specified shell. → tests.old/Cross-shell test support/The -s option should invoke tests with the specified shell.
View File

0
tests/Empty directories → tests.old/Empty directories
View File

0
tests/Exit codes of zero should pass. → tests.old/Exit codes of zero should pass.
View File

0
tests/Exit on fail if -e is passed. → tests.old/Exit on fail if -e is passed.
View File

0
tests/Failing tests should be marked in red. → tests.old/Failing tests should be marked in red.
View File

0
tests/Print version on -v. → tests.old/Print version on -v.
View File

0
tests/Setup and teardown/.test/setup → tests.old/Setup and teardown/.test/setup
View File

0
tests/Setup and teardown/.test/setup has run twice a → tests.old/Setup and teardown/.test/setup has run twice a
View File

0
tests/Setup and teardown/.test/setup has run twice b → tests.old/Setup and teardown/.test/setup has run twice b
View File

0
tests/Setup and teardown/.test/setup_dir → tests.old/Setup and teardown/.test/setup_dir
View File

0
tests/Setup and teardown/.test/setup_dir runs → tests.old/Setup and teardown/.test/setup_dir runs
View File

0
tests/Setup and teardown/.test/setup_dir runs only oncea → tests.old/Setup and teardown/.test/setup_dir runs only oncea
View File

0
tests/Setup and teardown/.test/setup_dir runs only onceb → tests.old/Setup and teardown/.test/setup_dir runs only onceb
View File

0
tests/Setup and teardown/.test/teardown → tests.old/Setup and teardown/.test/teardown
View File

0
tests/Setup and teardown/.test/teardown has run twice a → tests.old/Setup and teardown/.test/teardown has run twice a
View File

0
tests/Setup and teardown/.test/teardown has run twice b → tests.old/Setup and teardown/.test/teardown has run twice b
View File

0
tests/Setup and teardown/.test/teardown_dir → tests.old/Setup and teardown/.test/teardown_dir
View File

0
tests/Setup and teardown/_dir files should be run once per directory, and the others should be run once per file. → tests.old/Setup and teardown/_dir files should be run once per directory, and the others should be run once per file.
View File

0
tests/Subdirectories/Separate stuff → tests.old/Subdirectories/Separate stuff
View File

0
tests/Subdirectories/a/b/c/stuff → tests.old/Subdirectories/a/b/c/stuff
View File

0
tests/Succeeding tests should be marked in green. → tests.old/Succeeding tests should be marked in green.
View File

0
tests/TAP/.expected-output → tests.old/TAP/.expected-output
View File

0
tests/TAP/.testsuite/a → tests.old/TAP/.testsuite/a
View File

0
tests/TAP/.testsuite/b → tests.old/TAP/.testsuite/b
View File

0
tests/TAP/.testsuite/c → tests.old/TAP/.testsuite/c
View File

0
tests/TAP/Running with -t should produce TAP output. → tests.old/TAP/Running with -t should produce TAP output.
View File

0
tests/The setup script should not be sourced./A variable exported from setup should not be visible in an associated test script. → tests.old/The setup script should not be sourced./A variable exported from setup should not be visible in an associated test script.
View File

0
tests/The setup script should not be sourced./setup → tests.old/The setup script should not be sourced./setup
View File

0
tests/This test should succeed. → tests.old/This test should succeed.
View File

0
tests/Urchin should do a sanity check so that directories like the user home are not specified as tests./.foo/test/bar/baz → tests.old/Urchin should do a sanity check so that directories like the user home are not specified as tests./.foo/test/bar/baz
View File

0
tests/Urchin should do a sanity check so that directories like the user home are not specified as tests./.test/successful test → tests.old/Urchin should do a sanity check so that directories like the user home are not specified as tests./.test/successful test
View File

0
tests/Urchin should do a sanity check so that directories like the user home are not specified as tests./If Urchin is run on a file named something like "test", no Molly-guard should be presented. → tests.old/Urchin should do a sanity check so that directories like the user home are not specified as tests./If Urchin is run on a file named something like "test", no Molly-guard should be presented.
View File

0
tests/Urchin should do a sanity check so that directories like the user home are not specified as tests./The -f flag should disable the Molly-guard. → tests.old/Urchin should do a sanity check so that directories like the user home are not specified as tests./The -f flag should disable the Molly-guard.
View File

0
tests/Urchin should do a sanity check so that directories like the user home are not specified as tests./The Molly-guard should accept arguments that contain test in the middle. → tests.old/Urchin should do a sanity check so that directories like the user home are not specified as tests./The Molly-guard should accept arguments that contain test in the middle.
View File

0
tests/Urchin should do a sanity check so that directories like the user home are not specified as tests./Urchin should warn if it is run on something that does not look like a test. → tests.old/Urchin should do a sanity check so that directories like the user home are not specified as tests./Urchin should warn if it is run on something that does not look like a test.
View File

0
tests/Urchin should recognize that the filesystem is sane./.fixtures/bladyblah → tests.old/Urchin should recognize that the filesystem is sane./.fixtures/bladyblah
View File

0
tests/Urchin should recognize that the filesystem is sane./The bin directory should exist. → tests.old/Urchin should recognize that the filesystem is sane./The bin directory should exist.
View File

0
tests/Urchin should recognize that the filesystem is sane./The file "bladyblah" should contain the phrase "blah". → tests.old/Urchin should recognize that the filesystem is sane./The file "bladyblah" should contain the phrase "blah".
View File

0
tests/Urchin should recognize that the filesystem is sane./The filesystem root directory should exist. → tests.old/Urchin should recognize that the filesystem is sane./The filesystem root directory should exist.
View File

0
tests/Urchin should recognize that the filesystem is sane./The filesystem root should contain no "aoeuaoeuaoeu" file. → tests.old/Urchin should recognize that the filesystem is sane./The filesystem root should contain no "aoeuaoeuaoeu" file.
View File

0
tests/skip/.test/fail → tests.old/skip/.test/fail
View File

0
tests/skip/.test/skip → tests.old/skip/.test/skip
View File

0
tests/skip/.test/succeed → tests.old/skip/.test/succeed
View File

0
tests/skip/Skip on exit code 3. → tests.old/skip/Skip on exit code 3.
View File

0
tests/urchin exit code/.test/This test passes → tests.old/urchin exit code/.test/This test passes
View File

0
tests/urchin exit code/non zero exit code when a test fails → tests.old/urchin exit code/non zero exit code when a test fails
View File

0
tests/urchin exit code/zero exit code when tests all pass → tests.old/urchin exit code/zero exit code when tests all pass
View File