Item11466: UnitTestContrib claims to set FOSWIKI_ASSERTS, but doesn't
Priority: Urgent
Current State: Closed
Released In: n/a
Target Release: n/a
Applies To: Extension
Component: UnitTestContrib
Branches: Release01x01 trunk
Recent changes have borked unit tests, but the fails are not showing up presumably because the unit tests are not being run with ASSERTs enabled?
--
CrawfordCurrie - 23 Jan 2012
Hi Crawford, TestRunner claims rather proudly, when you run them:
exporting FOSWIKI_ASSERTS=1 for extra checking; disable by exporting FOSWIKI_ASSERTS=0
It hadn't occurred to me that this is in fact a lie.
Using this task to make TestRunner's noise less misleading.
--
PaulHarvey - 24 Jan 2012
Actually, I figured out a reliably failing unit test, and managed to fix it. No need to use
LocalLib
to set
FOSWIKI_ASSERTS
from LocalLib, I hope.
--
PaulHarvey - 24 Jan 2012
Test breakage arising from
Item11431 work can be fixed under that task. Closing
--
PaulHarvey - 24 Jan 2012