---
Bugs:

According to the SF trackers we are now down to 8 bugs, two of them
are sufficiently critical enough that they have to be fixed before a
new release can go out. These two bugs are:

SF1677584 "Cannot explicitly exclude categories for test run": Here we
need to extend the UI and the underlying logic so that it becomes
possible to explicitly state which categories should be excluded. The
resulting logic would then be that a test is run if it Included and
Not Excluded at the same time. The third state for a category can then
be "Don't Care" which means it will not be run if not included, but it
doesn't have to explicitly excluded. Note that all category settings
will be stored in the recipe, and the command line will read and apply
those settings as well.
We are currently working on this as not fixing it would mean that we
would remove existing functionality. In this case we don't want to do
that.

SF1680425 "Test hierarchy doesn't report location of failed
assertion": Just reporting a failed test is not sufficient. Each user
would like to have sufficient information about where it failed. This
bug, too, must be fixed before the next release.

---
New Features:

The next release will see an additional feature: the TestAttribute
will support an additional optional named parameter for a Timeout.
Here a user can specify the timeout in milliseconds and if the test
doesn't finish within that time, it will be reported as failed.

---

Timeline:
It all depends on how fast we can get the two above mentioned bugs
fixed. We are still shooting for March 31, but it has to go very well.


Thank you to all the people who provide feedback for your support!

Kind regards,
Manfred.
---
Manfred Lange.
csUnit team member
http://www.csunit.org