- Commit
- 3f7bdb1382cd3632cf813e165c4143bc8f7961d6
- Parent
- f320d9f9ea2f983d9a0f5d01f1235eef1df28f37
- Author
- John MacFarlane <jgm@berkeley.edu>
- Date
Renamed runtests.py -> spec_tests.py.
My personal build of CMark ✏️
Renamed runtests.py -> spec_tests.py.
4 files changed, 6 insertions, 6 deletions
Status | File Name | N° Changes | Insertions | Deletions |
Modified | CMakeLists.txt | 4 | 2 | 2 |
Modified | README.md | 4 | 2 | 2 |
Modified | spec.txt | 4 | 2 | 2 |
Renamed | runtests.py -> spec_tests.py | 0 | 0 | 0 |
diff --git a/CMakeLists.txt b/CMakeLists.txt @@ -23,7 +23,7 @@ enable_testing() # To get verbose output: cmake --build build --target "test" -- ARGS='-V' add_test(spectest_library - python "${CMAKE_SOURCE_DIR}/runtests.py" "--no-normalize" "--spec" + python "${CMAKE_SOURCE_DIR}/spec_tests.py" "--no-normalize" "--spec" "${CMAKE_SOURCE_DIR}/spec.txt" "--library-dir" "${CMAKE_BINARY_DIR}/src" ) add_test(pathological_tests_library @@ -38,7 +38,7 @@ if (WIN32) ) endif(WIN32) add_test(spectest_executable - python "${CMAKE_SOURCE_DIR}/runtests.py" "--no-normalize" "--spec" "${CMAKE_SOURCE_DIR}/spec.txt" "--program" "${CMAKE_BINARY_DIR}/src/cmark" + python "${CMAKE_SOURCE_DIR}/spec_tests.py" "--no-normalize" "--spec" "${CMAKE_SOURCE_DIR}/spec.txt" "--program" "${CMAKE_BINARY_DIR}/src/cmark" ) if(NOT CMAKE_BUILD_TYPE)
diff --git a/README.md b/README.md @@ -75,12 +75,12 @@ Or, to create Xcode project files on OSX: Tests can also be run manually on any executable `$PROG` using: - python runtests.py --program $PROG + python spec_tests.py --program $PROG If you want to extract the raw test data from the spec without actually running the tests, you can do: - python runtests.py --dump-tests + python spec_tests.py --dump-tests and you'll get all the tests in JSON format.
diff --git a/spec.txt b/spec.txt @@ -170,10 +170,10 @@ as a "syntax error," the divergence often isn't discovered right away. This document attempts to specify Markdown syntax unambiguously. It contains many examples with side-by-side Markdown and HTML. These are intended to double as conformance tests. An -accompanying script `runtests.py` can be used to run the tests +accompanying script `spec_tests.py` can be used to run the tests against any Markdown program: - python runtests.py --spec spec.txt --program PROGRAM + python spec_tests.py --spec spec.txt --program PROGRAM Since this document describes how Markdown is to be parsed into an abstract syntax tree, it would have made sense to use an abstract
diff --git a/runtests.py b/spec_tests.py