This is an automated email from the git hooks/post-receive script.

guillem pushed a commit to branch master
in repository dpkg.

View the commit online:
https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=afebdb5b96f71aaadbc16f3e21cc6984dec0873f

commit afebdb5b96f71aaadbc16f3e21cc6984dec0873f
Author: Guillem Jover <[email protected]>
AuthorDate: Tue Feb 1 05:33:42 2011 +0100

    Add new README file
---
 README | 38 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)

diff --git a/README b/README
new file mode 100644
index 000000000..85b7694ed
--- /dev/null
+++ b/README
@@ -0,0 +1,38 @@
+dpkg functional test-suite
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+How to run
+----------
+
+There's a brief usage information when invoking “make” on the topdir.
+
+The DPKG_TESTSUITE_OPTIONS environment/make variable can be used to change
+the behaviour of the test runs, the following options are currently
+supported:
+
+* test-all
+
+  This runs all tests, including manual and failing ones.
+
+* local-db
+
+  This uses a local database, which speeds greatly the runs, but requires
+  1.16.0 (unreleased at the time of this writing).
+
+Test-suite layout
+-----------------
+
+The tests are split into logical units, testing a specific characteristic.
+To add a new test please check Test.mk and Makefile on the topdir, and some
+of the current tests. Patches welcome!
+
+Future plans
+------------
+
+There's lots of tests that are still missing, we are adding new ones when
+we stumble over regressions, when adding new functionality, and as time
+permits for existing functionality.
+
+The idea is for this to eventually be merged into the dpkg git repository
+and be run as part of “make check”. Some changes to dpkg would need to be
+implemented first.

-- 
Dpkg.Org's dpkg

Reply via email to