2006-01-09 Frank Ch. Eigler <fche@redhat.com>

	* HACKING: Extend guidelines for tapset testing.

diff --git a/ChangeLog b/ChangeLog
index 0c857bbac8c34b0495efecad765b1cf06a7fd7d8..ebfa15c664625ce4bac272838a05e1d89457bbb5 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2006-01-09  Frank Ch. Eigler  <fche@redhat.com>
+
+       * HACKING: Extend guidelines for tapset testing.
+
 2006-01-06  Will Cohen  <wcohen@redhat.com>
 
        * Makefile.am (gcov,lcov): Don't remove .gcno .gcda files.

diff --git a/HACKING b/HACKING
index 2be2fc0f18a534d62e918cdf14186f4f511b5cdc..09acecf6c0826c284ead403204aa6d94d7f707f6 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -72,11 +72,14 @@ the <systemtap@sources.redhat.com> mailing list.
   identifiers should be prefixed with "_" for extra uniqueness, and
   not documented in the man pages.
 
-  New or changed embedded-C code should be accompanied by a test case
-  in the /src/testsuite/buildok/ bucket to assert its buildability,
-  and ideally pass-5 tests to assert correct behavour.  Embedded-C
-  code should avoid making references to the runtime or other code
-  possibly generated by the translator.
+  Tapsets should come with a tests cases that provide good test coverage.
+  Every alias definition should be tested for pass-2 correctness.  Every
+  embedded-C routine should be tested for pass-4 buildability and ideally
+  pass-5 correctness.  The platforms/architectures against which the tapset
+  was tested should be published, and ideally asserted by code.
+
+  Embedded-C code should avoid making references to the runtime or
+  other code possibly generated by the translator.
 
 - runtime