Ok. I'm on board with doing manual web tier testing to make sure
things are decent for the 2.6 launch.
2. Did we ever make a decision to require JavaScript to do even
minimal things like registering users?
No. Then again, we never decided NOT to require it either. In
fact, we never discussed accessibility requirements for JSPWiki.
As much with open source, things just... happen.
Fair enough. Shall we discuss accessibility requirements, then? ;)
Depends. The simple short term solution is that we could drop in
the old default template (as "olddefault"), and use that. It should
really work with minimal modifications (the editors would need to be
fixed to conform to the new SpamFilter policies).
I'd rather stick with the new template and manually test it. I like
the new one quite a bit.
A concrete proposal would be that instead of trying to fix something
that we're planning to ditch anyway, we could split the existing
unit tests among the developers on this list (should amount to a few
per person, tops), and have everyone examine the code and run them
manually. Then collect the results on a single wikipage.
Let's do it. Remember that we've got 5 scenarios, though, based on
different combinations of container/custom/JDBC/XML user databases.
Then fix any excess bugs, release 2.6, move code to Apache, and
write a big, bold issue report "Web tests need a-fixin'" and make it
block 2.8. And hope someone takes it to heart to start working on
it...
Assuming do as Janne suggests, and fix web tier tests in 2.8 -- I'd
like to suggest that we think collectively about what we need for web
unit testing. Here are my priorities:
- Must run as part of an automated Ant build script
- Must return results on the command line as part of the build (no
manual inspection of report files needed)
- Must support JavaScript
- Should be very easy to code new tests with
- Should work with JUnit so we can run tests inside the IDE if needed
Dirk, regarding using two web unit testing tools (one for non-JS tests
and one for JS-related-tests): I don't think this is a good idea.
Let's find one tool that works in both scenarios. I thought Selenium
might be that tool, but its incompatibility with Mootools rules it out
for now.
Question: how much dependency do your scripts have on Mootools? Would
it be hard to switch to Prototype or Dojo? I certainly don't want the
testing tail to wag the coding dog here, but I thought I'd ask. As it
happens, the Stripes guys say nice things about Prototype.
Andrew
