diff options
author | Caio Marcelo de Oliveira Filho <caio.oliveira@intel.com> | 2015-03-05 13:06:38 -0300 |
---|---|---|
committer | Lucas De Marchi <lucas.demarchi@intel.com> | 2015-03-05 23:56:44 -0300 |
commit | f4f408f9f37cbc18a7c42c05591964684287cb76 (patch) | |
tree | e7995c4ed756399b5cd874d9c7f03c07fb0b7a00 | |
parent | 0f079cba76fcd10544798aa8d2318975d9a7e7fd (diff) | |
download | kmod-f4f408f9f37cbc18a7c42c05591964684287cb76.tar.gz |
testsuite: update README
-rw-r--r-- | testsuite/README | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/testsuite/README b/testsuite/README index d5843bf..6efc61e 100644 --- a/testsuite/README +++ b/testsuite/README @@ -33,7 +33,7 @@ pay attention when writing a test: 3 - If you want testsuite to compare the stdout/stderr of your tests in order to check if it worked or not, fill in output.{stderr,stdout} the file with - the expected output. Bare in mind the same file is used for all + the expected output. Bear in mind the same file is used for all architectures, so don't print arch-dependent content if you are comparing the output. @@ -49,8 +49,10 @@ pay attention when writing a test: 6 - expected_fail: if that test is expected to fail, i.e. the return code is expected not to be 0. -7 - If you added files to the rootfs, be sure to compact it back to - rootfs.tar.xz before sending patches: use 'make testsuite-pack-rootfs' +7 - The rootfs is populated by copying the entire contents of rootfs-pristine + then running populate-modules.sh to copy generated modules from + module-playground. Update the latter script to include any modules your + test need. 8 - Tests can be run individually, outside of 'make check'. strace and gdb work too, as long as you tell them to operate on child process. |