X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=blobdiff_plain;f=testing%2Findex.html;h=af3ce934822cb036894024e8624e8185b1c449bc;hp=7e5fcb030a199722ad2d09c562e67e9a707cbdf0;hb=a4d50544de07f13e3f9644d2b48e41ebdc91a7a3;hpb=8a162e5e063fbbd6be04568e29633fad8f8b6720 diff --git a/testing/index.html b/testing/index.html index 7e5fcb030a..af3ce93482 100644 --- a/testing/index.html +++ b/testing/index.html @@ -7,7 +7,7 @@ A release test must be done on code committed to git. Commit, then test. That way one can know for sure *what* code was actually tested.

- Note that this testing document does not have anything to do with testing that is done + Note that this testing document does not have anything to do with testing that is done before committing to git. It is a test document for released code. Pre-commit testing is done mostly by the developer who has written the change. Sometimes code is committed to synchronize work, even if it has known problems. Release testing is @@ -16,7 +16,7 @@ and test setup. Also the testing will take place over an extended period of time.

All of the above makes it imperative that there can be no doubt about *which* code - is tested and thus all tests refer to committed code by subversion number. + is tested and thus all tests refer to committed code by subversion number.

Release procedure

OpenOCD mainline is work in progress. Expect it to change daily and to have some quirks. @@ -35,7 +35,7 @@

Test cases

Additionally OpenOCD has test cases that target specific functionality more precisely.

- A full release test must include both smoketests and unit testing. + A full release test must include both smoketests and unit testing.

Test cases