File: TODO

package info (click to toggle)
squid3 3.0.PRE5-5%2Betch2
  • links: PTS
  • area: main
  • in suites: etch
  • size: 21,188 kB
  • ctags: 20,388
  • sloc: cpp: 119,851; ansic: 30,259; sh: 10,465; makefile: 3,289; perl: 1,267; awk: 84; xml: 58
file content (44 lines) | stat: -rw-r--r-- 1,734 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
* Bugs:
Asserter::makeNotEqualMessage() strip the shortDescription of the additional message.

* CppUnit:
  - Extends CompilerOutputter to a generic text outputter that can use a format string
    to display both the location of the failure and the message.
  - STL concept checker.
  - Memory leak tracking: setUp/tearDown should be leak safe if no failure occured.

* UnitTest
  - add tests for XmlOutputter::setStyleSheet (current assertion macro strip <?...> when
    testing )
  - add tests for TestRunner, TextUi::TestRunner, CompilerOutputter.
  - add tests for test plug-in

* VC++ TestRunner:
  - Modify MfcUi::TestRunner to expose TestResult (which allow specific TestListener
    for global initialization).
  - Update MfcTestRunner to use TestPath to store test in the registry
  - [DONE] Add "details" field to show detail of the selected failed test:
    - suite and test name,
    - failure message. If possible separate "was" and "expected" in the
      forthcoming assertEquals() to make comparison easier,
    - source file location. 
    
* Documentation:
	CookBook:
	- how to create simple test cases (with CppUnit namespace)
	  - test case using only CPPUINT_ASSERT
	  - test case using CPPUNIT_ASSERT_EQUAL
	  - advanced assertions with the CPPUNIT_ASSERT_MESSAGE
	- Helper Macros for convenience
	- Creating a suite
	- Composing a suite from more suites (i.e. compose tests for n modules to
	  form a big test for the whole program)
	- customizing output using an user defined TestListener
	  - how to write the TestListener (subclass of TestListener)
	  - how to hook it in
	- how to use the GUI
	  - MSVC++ special stuff
	- other custmization stuff I haven't understood yet

	CppUnit: architecture overview.