- Timestamp:
-
08/28/12 22:53:36 (12 years ago)
- Author:
-
Xiaochen Pan
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v17
|
v18
|
|
5 | 5 | I compared 10 testing framework by unit testing functionality and mocking capability.For each framework, I modified several tests from current test suite, compile them with RTEMS compilers, simulate the new tests with Sparc architecture, and compare the results to ensure that framework used could work correctly for RTEMS based testing. |
6 | 6 | |
7 | | The detailed test framework review can be accessed with this link: |
8 | | |
9 | | [wiki:Projects/GSoC/TestingReview TestingReview] |
| 7 | The detailed test framework review can be accessed with this link: [wiki:Projects/GSoC/TestingReview TestingReview] |
10 | 8 | |
11 | 9 | Please click on the name of each testing framework to see the detailed comparison note and sanity check result. |
… |
… |
|
24 | 22 | The conversion plan contains the detailed testing plan, which is a table of the subareas within each functional area, for example, memory management. It also maps the already written tests in the current test suites to the subareas in the table. The blank element under Written Tests column indicates that there is no tests written in current test suite that exclusively tests this subarea. It does not necessarily mean that this subarea is not covered in current test suites. The tests for this subarea may be included in tests written for its parent area. Otherwise, it is not written yet. |
25 | 23 | |
26 | | [wiki:Projects/GSoC/TestSuite/conversion_plan Conversion Map] |
| 24 | Please access the conversion map via this link: [wiki:Projects/GSoC/TestSuite/conversion_plan Conversion Map] |
27 | 25 | = Design New Test Framework Interface = |
28 | 26 | |