Community
Participate
Working Groups
In current builds, html.core and css.core unit tests fail, even though they work correctly when ran in dev. envonment. The (primary) reason for this, is that the tests looks for some "reference files" to compare current results against. The problem is, that it looks for these reference files in a directory matching plugin ID, but on build machine, the directory is named pluginID_1.0.0. A better approach is to zip up the reference files, and unzip them into target workspace, as we do for encoding tests ... and then compare current results with those reference files in the target workspace. The current results would also have to be written to target workspace, instead of directly to file system.
Marking as P2, since unit tests should be working for milestone 2.
Decided to leave this bug open, and fix next Milestone, in the interest of simplity. The failing unit tests will be removed from current suite. This isn't a bad sign, since when run "locally" they do run ok, so its just a test improvement. Test improvements can be done later.
Changed abstract since Phil (I think it was) found the tests were broken due to simple build error (reference files were no in build.properties file). But, I still think its a good idea to use workspace, instead of direct file system, so have changed to "enhancement".
not very important, but, maybe someone would want to help improve this tests in this small way.
Hi, everyone. This bug was opened in 2004. David's comment in 2007 asked for improving the test. Is there still a need for that? Thanks. Peter.
I don't think this is something that will be gotten around to.
