summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Hutterer <peter.hutterer@who-t.net>2011-07-22 08:08:07 +1000
committerPeter Hutterer <peter.hutterer@who-t.net>2011-07-22 08:08:07 +1000
commita0d6b1c777e5aff80c724259855ee1d359f5b470 (patch)
treeca1e1b9acbdde860435f28f59079482415fbb6a0
Add README for functionality outline.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-rw-r--r--README32
1 files changed, 32 insertions, 0 deletions
diff --git a/README b/README
new file mode 100644
index 0000000..623af09
--- /dev/null
+++ b/README
@@ -0,0 +1,32 @@
+iltest is a test framework for InterLeaved TESTing. It was originally
+written for X.Org X Server testing.
+
+The principle: A process (the "testee") need to be tested by other processes
+(the "tester(s)"). The testers report on whether the tests were successful.
+
+A test has three stages:
+- pre: preparation stage
+- run: actual testing stage
+- post: cleanup stage
+
+In iltest, the order of calls is thus:
+
+ Time Testee Tester
+ | pre()
+ | pre()
+ | run()
+ | run()
+ | post()
+ V post()
+
+Thus, in the case of the X server testing, usually this happens:
+ testee.pre: back up various files, ensure system integrity, etc.
+ tester.pre: set up configuration files, add virtual devices, etc.
+ testee.run: run the X server
+ tester.run: run tests
+ testee.post: restore files
+ tester.post: gather test results
+
+iltest itself does not do much. It simply provides the interfaces for the
+test suites (which contain most of the knowledge) and a few utility
+functions.