From 35772868bbd02f4f72a19aa1e24772d423a21312 Mon Sep 17 00:00:00 2001 From: Jean Privat Date: Mon, 6 Jun 2016 14:21:58 -0400 Subject: [PATCH] nitunit: update man page about test-suite Signed-off-by: Jean Privat --- share/man/nitunit.md | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/share/man/nitunit.md b/share/man/nitunit.md index 2f07fd5..2bec157 100644 --- a/share/man/nitunit.md +++ b/share/man/nitunit.md @@ -129,12 +129,12 @@ This flag can be used by libraries and program to prevent (or limit) the executi ## Working with `TestSuites` -TestSuites are Nit files that define a set of `TestSuite`s for a particular -module. +TestSuites are Nit modules that define a set of TestCases. -The test suite’s module must be called `test_` followed by the name of the -module to test. So for the module `foo.nit` the test suite will be called -`test_foo.nit`. +A test suite is a module that uses the annotation `is test_suite`. + +It is common that a test suite focuses on testing a single module. +In this case, the name of the test_suite is often `test_foo.nit` where `foo.nit` is the tested module. The structure of a test suite is the following: @@ -321,9 +321,6 @@ Only run test case with name that match pattern. Examples: `TestFoo`, `TestFoo*`, `TestFoo::test_foo`, `TestFoo::test_foo*`, `test_foo`, `test_foo*` -### `-t`, `--target-file` -Specify test suite location. - ### `--autosav` Automatically create/update .res files for black box testing. -- 1.7.9.5