<meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
<body>
- <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>
+ OpenOCD trunk is work in progress. Expect it to change daily and to have some quirks.
+ <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 seeing. Testing work and bug reports are highly appreciated.</p>
<p>The OpenOCD community may decide to create release branches. If this happens, then a branch will be created from OpenOCD trunk. The particular version to create that branch might be an older version rather than the latest and greatest. Fixes are then ported to that release branch from OpenOCD trunk.</p>
<h2>Vocabulary</h2>
<table border="1">
<tr>
<td width="100">Passed version</td>
- <td>The latest version on which the test is known to pass</td>
+ <td>The latest version on which the test is known to pass.</td>
</tr>
<tr>
<td width="100">Broken version</td>
</tr>
<tr>
<td width="100">ID</td>
- <td>A unqiue ID to refer to a test. The unique numbers are maintained in this file.</td>
+ <td>A unique ID to refer to a test. The unique numbers are maintained in this file.</td>
</tr>
</table>
<p></p>
<th align="center" width="110">Passed version</th>
<th align="center" width="110">Broken version</th>
</tr>
+ <tr>
+ <td width="65">fill_malloc</td>
+ <td width="165">Fill malloc() memory with garbage</td>
+ <td align="center" width="110">n/a</td>
+ <td align="center" width="110">n/a</td>
+ <td align="center" width="110">n/a</td>
+ </tr>
<tr>
<td width="65">ocd1</td>
<td width="165">Telnet Windows</td>
</tr>
<tr>
<td width="65"><a href="#bdte-ram">bdte-ram</a></td>
- <td width="165">str710 ram debugging</td>
+ <td width="165">str710 RAM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-rom">bdte-rom</a></td>
- <td width="165">str710 rom debugging</td>
+ <td width="165">str710 ROM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-ram">bdte-ram</a></td>
- <td width="165">str912 ram debugging</td>
+ <td width="165">str912 RAM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-rom">bdte-rom</a></td>
- <td width="165">str912 rom debugging</td>
+ <td width="165">str912 ROM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-ram">bdte-ram</a></td>
- <td width="165">lpc2148 ram debugging</td>
+ <td width="165">lpc2148 RAM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-rom">bdte-rom</a></td>
- <td width="165">lpc2148 rom debugging</td>
+ <td width="165">lpc2148 ROM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-ram">bdte-ram</a></td>
- <td width="165">lpc2294 ram debugging</td>
+ <td width="165">lpc2294 RAM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-rom">bdte-rom</a></td>
- <td width="165">lpc2294 rom debugging</td>
+ <td width="165">lpc2294 ROM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-ram">bdte-ram</a></td>
- <td width="165">sam7s256 ram debugging</td>
+ <td width="165">sam7s256 RAM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-rom">bdte-rom</a></td>
- <td width="165">sam7s256 rom debugging</td>
+ <td width="165">sam7s256 ROM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-ram">bdte-ram</a></td>
- <td width="165">sam7x256 ram debugging</td>
+ <td width="165">sam7x256 RAM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-rom">bdte-rom</a></td>
- <td width="165">sam7x256 rom debugging</td>
+ <td width="165">sam7x256 ROM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
</tr>
<tr>
<td width="65"><a href="#bdte-ram">bdte-ram</a></td>
- <td width="165">at91r40008 ram debugging</td>
+ <td width="165">at91r40008 RAM debugging</td>
<td align="center" width="110">JTAGkey</td>
<td align="center" width="110">423</td>
<td align="center" width="110">n/a</td>
<h1>Policy on removing features from OpenOCD</h1>
If a feature in OpenOCD is known to be broken and nobody has submitted a fix and the feature is causing trouble for maintainence, it can be removed from OpenOCD trunk. The threshold for temporarily removing something from OpenOCD trunk is low to ease maintainence and place the burden of maintainence on those that care about a feature.
<p>Note that code is never deleted from OpenOCD svn, it remains in svn so if somebody sees a feature removed that they would like kept, they have but to port and fix that feature back up to main trunk. This document can be helpful in this regard in that the latest working version and the known broken version may be listed.</p>
- <h1>Policy on adding features from OpenOCD</h1>
+ <h1>Policy on adding features to OpenOCD</h1>
To add a feature to OpenOCD, generally it should not break any existing features and it should be functional and the code reasonably readable and useful to others in the OpenOCD community. The code does not have to be completed. Work in progress is fine for OpenOCD trunk.
<p>Also new tests should be defined. Note that the code does not have to pass all the tests. In fact it can be helpful to have tests to describe facets that really should be working, but aren't done yet. </p>
<hr>
<h1>ocd4 - ARM7 debugging<a name="test_ocd4"></a></h1>
- Connect to ARM7 device(any), use GDB load to load a program into RAM and single halt, resume and single step.
+ Connect to ARM7 device (any), use GDB load to load a program into RAM and single halt, resume and single step.
<hr>
<h1>bdte-ram (Basic debugging test with Eclipse in RAM)<a id="bdte-ram" name="bdte-ram"></a></h1>
<p>This test was made under Eclipse with the Zylin Embedded CDT plugin. For the GDB "Initialize commands" take a look in the examples/<target>/prj/<b>eclipse_ram.gdb</b> file.</p>
<p></p>
</body>
-</html>
\ No newline at end of file
+</html>
projects / fw / openocd / blobdiff