wrote up explaining why tests are done on committed code.
authoroharboe <oharboe@b42882b7-edfa-0310-969c-e2dbd0fdcd60>
Sat, 1 Mar 2008 21:40:48 +0000 (21:40 +0000)
committeroharboe <oharboe@b42882b7-edfa-0310-969c-e2dbd0fdcd60>
Sat, 1 Mar 2008 21:40:48 +0000 (21:40 +0000)
git-svn-id: svn://svn.berlios.de/openocd/trunk@427 b42882b7-edfa-0310-969c-e2dbd0fdcd60


index df9e81a1a3602d94c2fe246ce3610be63a8ed34a..267c2a7be33353dd467296ffc5a1c6d857d44aaa 100644 (file)
@@ -3,8 +3,18 @@
        <meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
-               <h1>Testing</h1>
-               A test should be done on code committed to svn. Commit, then test. That way one can know for sure *what* code was actually tested.
+               <h1>Release testing</h1>
+               A release test must be done on code committed to svn. Commit, then test. That way one can know for sure *what* code was actually tested.
+               <p>
+               Note that this testing document does not have anything to do with testing that is done 
+               before committing to svn. It is a test document for released code. Pre-commit testing
+               is done mostly by the developer who has written the change. Release testing is
+               done on code believed to be stable, often a couple of weeks old, and not by
+               the developers, but rather users and community testers who has the requisite hardware
+               and test setup. Also the testing can take place over an extended period of time.
+               <p>
+               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.  
                <h1>Release procedure</h1>
                OpenOCD trunk is work in progress. Expect it to change daily and to have some work in progress.
                <p>If you need the latest released and tested version, look for binary snapshots of OpenOCD. Worst case look up the test result table below for the features that are important to you and extract and build the version that has the right cocktail of working features for you. You can also work with the community to address the problems you are seing. Testing work and bug reports are highly appreciated.</p>

Linking to existing account procedure

If you already have an account and want to add another login method you MUST first sign in with your existing account and then change URL to read https://review.openocd.org/login/?link to get to this page again but this time it'll work for linking. Thank you.

SSH host keys fingerprints

1024 SHA256:YKx8b7u5ZWdcbp7/4AeXNaqElP49m6QrwfXaqQGJAOk gerrit-code-review@openocd.zylin.com (DSA)
384 SHA256:jHIbSQa4REvwCFG4cq5LBlBLxmxSqelQPem/EXIrxjk gerrit-code-review@openocd.org (ECDSA)
521 SHA256:UAOPYkU9Fjtcao0Ul/Rrlnj/OsQvt+pgdYSZ4jOYdgs gerrit-code-review@openocd.org (ECDSA)
256 SHA256:A13M5QlnozFOvTllybRZH6vm7iSt0XLxbA48yfc2yfY gerrit-code-review@openocd.org (ECDSA)
256 SHA256:spYMBqEYoAOtK7yZBrcwE8ZpYt6b68Cfh9yEVetvbXg gerrit-code-review@openocd.org (ED25519)
+--[ED25519 256]--+
|=..              |
|+o..   .         |
|*.o   . .        |
|+B . . .         |
|Bo. = o S        |
|Oo.+ + =         |
|oB=.* = . o      |
| =+=.+   + E     |
|. .=o   . o      |
2048 SHA256:0Onrb7/PHjpo6iVZ7xQX2riKN83FJ3KGU0TvI0TaFG4 gerrit-code-review@openocd.zylin.com (RSA)