- Timestamp:
-
03/01/11 06:53:11 (13 years ago)
- Author:
-
JoelSherrill
- Comment:
-
/* RTEMS Testing */
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v201
|
v202
|
|
32 | 32 | |
33 | 33 | |
34 | | Testing a large body of software like RTEMS is in a continual state |
35 | | of improvement. There is always a need for more test cases and easier |
36 | | ways to run them all and decode the results. In addition, we want to be |
37 | | able to run all tests on as many hardware and simulator configurations |
38 | | as possible. Some of the identified activities which would augment our |
39 | | testing capabilities are listed here: |
| 34 | Testing a large body of software like RTEMS is in a continual state of improvement. There is always a need for more test cases and easier ways to run them all and decode the results. In addition, we want to be able to run all tests on as many hardware and simulator configurations as possible. Testing doesn't sound exciting to most people but when you combine the breadth of what we need to test with our desire for 100% instruction and branch path coverage, you get some very interesting and challenging work. |
| 35 | |
| 36 | Some of the identified activities which would augment our testing capabilities are listed here: |
40 | 37 | |
41 | 38 | * [wiki:Testing/Filesystem File System Test Suite] |