diff options
| author | fche <fche> | 2006-01-09 18:14:58 +0000 |
|---|---|---|
| committer | fche <fche> | 2006-01-09 18:14:58 +0000 |
| commit | a9a29deb6ee0f9e38dea288e12477acb5f672f32 (patch) | |
| tree | 981298c7c3421bd65913e93bc70780e2cffb53d6 /HACKING | |
| parent | e885b2ec5c2f7731b439c299628a6a634ff7e46e (diff) | |
| download | systemtap-steved-a9a29deb6ee0f9e38dea288e12477acb5f672f32.tar.gz systemtap-steved-a9a29deb6ee0f9e38dea288e12477acb5f672f32.tar.xz systemtap-steved-a9a29deb6ee0f9e38dea288e12477acb5f672f32.zip | |
2006-01-09 Frank Ch. Eigler <fche@redhat.com>
* HACKING: Extend guidelines for tapset testing.
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 13 |
1 files changed, 8 insertions, 5 deletions
@@ -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 |