sorry .. i thought i answered this.
i was using an older version of MXUnit i guess. seemed to work with
minimal effort. to be honest i can't recall as I have never had the
need to update it. we have a version that ships with the nightly WAR
as the unit tests for some of the functions
On 21/08/2013 00:43, Aaron J. White wrote:
Hello all, am I beating down a dead end? Does OpenBD lack a good unit
test framework?
On Tuesday, August 6, 2013 12:27:24 PM UTC-5, Aaron J. White wrote:
Hello all,
I recently used MXunit with the OpenBD nightly and came across a
ton of odd issues. Before I make any assumptions I would like to
know if anyone else on this list uses MXunit with OpenBD and if
there are any known issues that I should be aware of.
One issue I stumbled across was that simple testing would error
out if I used a cfc that was in 100% cfscript. Changing the cfc to
use a component+cfscript tag in the beginning at least let the
test complete.
Another issue is that on some failing test cases MXunit will
complain about missing framework functions even though these
functions are clearly visible in the MXunit code.
I am using the vanilla Mxunit web interface without the eclipse
plugin (I don't like eclipse).
I can give more concrete examples and error messages if anyone is
interested.
Thank you,
Aaron J. White
--
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
---
You received this message because you are subscribed to the Google
Groups "Open BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
--
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
---
You received this message because you are subscribed to the Google Groups "Open BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
