bittersweetryan
commented
12 years ago Thanks Grant, you bring up some good points here. The first thing is due to the testing framework, some of them are programmed to stop after the first failed test. The ordering of the tests is also a limitation of the framework.
These might be a good thing to bring up to Marc Escher for possibly adding to MXUnit. This project actually spawned a previous commit I did to MXUnit 2.1 to order tests within a suite. It'd be nice if this project could help add more neat things to MXUnit.
Another thought I had would be to use jQuery to hide the failed tests, this would be super easy and the quickest approach. , however I think doing it within MXUnit would help speed up the tests which would be nice.
I spent the weekend playing with Python Koans. What I especially love about the Python Koans is that when you run the script, you are presented with a single failing test. You open the file, navigate to the test that is failing, make your changes, and on to the next test you go.
This is what I don't like about ColdFusion Koans currently. When you access the MXUnit tests page, you see a huge page listing all the failed tests. This may have been okay initially with just a few test, but the page is getting much longer as we add more tests. I find this screen of every test that failed to be very distracting and I think it probably distracts the user from learning ColdFusion.
In addition, the tests are not ordered. I know they are suppose to be ... and maybe in Railo or OpenBD they are, but I'm running ColdFusion 9 Developer Edition and the test are not in order whatsoever. I have not changed the mxunit folder or anything. This is extremely distracting when using ColdFusion Koans.
I think both of these issues can be addressed and improved upon and I'm willing to help do it.
But first, your thoughts?