Properties Output, Plan, Count and Last were added to read the current
test state (plan, how many tests were run, the test number of the last
run test). In particular, allow the reconfiguration of the Output stream
after the object is created.
* BUG: Fix reading XML comments and CDATA tags when they contain
characters that belong to the end tag while not forming a complete one.
* BUG: Fix returning value of XML comments.
[GB.XML.HTML]
* BUG: Fix reading lowercase HTML doctypes.
[DEVELOPMENT ENVIRONMENT]
* NEW: Form editor: Use text colors and not tooltip colors for information panel. Tooltip colors are sometimes unreadable.
* NEW: Image editor: Use text colors and not tooltip colors for information panel.
[GB.QT4]
* BUG: Don't use QFont::setStyleName() if Qt version is not at least 4.8.
[GB.QT5]
* BUG: Call QFont::setStyleName() last, as it may be buggy if Qt version is not at least 5.3.
[DEVELOPMENT ENVIRONMNENT]
* BUG: Main window: Fix an english mistake in a menu entry.
* NEW: Open project dialog: Always select the project filter text.
[GB.CHART]
* BUG: Fixed a bug in Chart class.
A more complex calculated id is now used. This let us use more than one chart.
* BUG: Fixed a bug in _CSerie class.
A call to an unexisting property Labels has been changed.
[DEVELOPMENT ENVIRONMENT]
* BUG: Farm client: Compile the project before publishing it, so that the project version is accurate in the case it is read from a VERSION file.
* BUG: Property sheet button icon is now different from project properties button icon.
TestHarness is a class which runs multiple tests and collects statistics
about them. It is inspired by perl's Test::Harness. It is the main
component of a program which tests other programs which output TAP.
The current design I'm implementing requires that unit tests are
implemented in classes outside of the unit they are testing, for the
following reasons:
1. You should only test public interface anyway. Even if it is
sometimes simpler to implement a test using private data of
an object:
2. It makes the class unnecessarily big and exposes methods which
you don't want/need for a release.
This base class for implementing tests comes next. Tests are run in
an external process, by using the test as a startup class. This has
the benefit that the test harness isn't affected by a crash in the
test. It would be nice to have special treatment of tests in the
project directory structure, to list all tests in a project reliably
from the outside. IDE and compiler could benefit from that as well.
The Test Anything Protocol (TAP) is a text-based format for communicating
unit test results. It originated from perl and has a specification here:
http://testanything.org/
[DEVELOPMENT ENVIRONMENT]
* NEW: Move lock icons to the right of the toolbar.
* NEW: Remove some unused icons.
* BUG: Form editor: String controls can be used as toolbar expander now.
* NEW: Project tree: symbolic link emblem should be more visible now.
[GB.FORM]
* NEW: DateChooser: Raise a Click event when a date is clicked in the inner calendar.
* NEW: DateBox: Clicking on a date automatically closes the date chooser popup.
