diff options
-rw-r--r-- | docs/style-guide.txt | 20 |
1 files changed, 0 insertions, 20 deletions
diff --git a/docs/style-guide.txt b/docs/style-guide.txt index ddf3ebb83..1f06662ac 100644 --- a/docs/style-guide.txt +++ b/docs/style-guide.txt | |||
@@ -607,23 +607,3 @@ illustrates emphasizing logical blocks: | |||
607 | /* clean up */ | 607 | /* clean up */ |
608 | free(line); | 608 | free(line); |
609 | } | 609 | } |
610 | |||
611 | |||
612 | Testing Guidelines | ||
613 | ~~~~~~~~~~~~~~~~~~ | ||
614 | |||
615 | It's considered good form to test your new feature before you submit a patch | ||
616 | to the mailing list, and especially before you commit a change to CVS. Here | ||
617 | are some guidelines on testing your changes. | ||
618 | |||
619 | - Always test busybox applets against GNU counterparts and make sure the | ||
620 | behavior / output is identical between the two. | ||
621 | |||
622 | - Try several different permutations and combinations of the features you're | ||
623 | adding and make sure they all work. (Make sure one feature does not | ||
624 | interfere with another, etc.) | ||
625 | |||
626 | - Make sure you test compiling against the source both with the feature | ||
627 | turned on and turned off in Config.h and make sure busybox compiles cleanly | ||
628 | both ways. | ||
629 | |||