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.
<p>
- 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
and test setup. Also the testing will 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.
+ is tested and thus all tests refer to committed code by subversion number.
<h1>Release procedure</h1>
OpenOCD mainline is work in progress.
Expect it to change daily and to have some quirks.
<h2>Test cases</h2>
Additionally OpenOCD has test cases that target specific functionality more precisely.
<p>
- A full release test must include both smoketests and unit testing.
+ A full release test must include both smoketests and unit testing.
<p>
<a href="testcases.html">Test cases</a>
</body>