| 1 | [[BackLinksMenu]] |
| 2 | |
| 3 | [[TicketQuery(summary=UNPLANNED_UNIT_TEST_FIX_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]] |
| 4 | |
| 5 | = Analysis = |
| 6 | |
| 7 | |
| 8 | == Overview == |
| 9 | Automatic tests need to be improved. Latest Hudson build reports 288 test failures out of 962 tests. |
| 10 | |
| 11 | == Task requirements == |
| 12 | * Revise the current unit tests |
| 13 | * Remove any useless test cases (for more, see implementation idea). |
| 14 | * Make as much as possible tests / demos to work. This includes improving the source if tests report problems. |
| 15 | * Writing new tests is not required for this revision, since it is too much effort. |
| 16 | |
| 17 | |
| 18 | == Task result == |
| 19 | Removed useless tests, others - passing. |
| 20 | |
| 21 | == Implementation idea == |
| 22 | Read about how to write good unit tests, [wiki:PLATROFM_STANDARDS_AUTOMATIC_TESTING] for documented convensions for testing and "Code smells" in the internal backlog. Look also at the available demos. In the design (or implementation) describe what needs to be removed, what will be repaired and what tests need to be written during the next revision. |
| 23 | |
| 24 | == Related == |
| 25 | [wiki:PLATFORM_STANDARDS_AUTOMATING_TESTING] |
| 26 | |
| 27 | == How to demo == |
| 28 | Run all the available tests. |
| 29 | |
| 30 | = Design = |
| 31 | ^(Describe your design here.)^ |
| 32 | |
| 33 | = Implementation = |
| 34 | ^(Describe and link the implementation results here (from the wiki or the repository).)^ |
| 35 | |
| 36 | = Testing = |
| 37 | ^(Place the testing results here.)^ |
| 38 | |
| 39 | = Comments = |
| 40 | ^(Write comments for this or later revisions here.) |