On Thu, May 30, 2013 at 10:58 PM, Olemis Lang <[email protected]> wrote:
> My conclusions after recent work attempting to run Trac functional > test suite against fresh Bloodhound testing environments > > 1. there's a notable performance penalty > when executing `wiki bh-upgrade` trac-admin command > 2. The whole testing infrastructure relies upon > HTTP Basic auth rather than Digest > > so ... Q's > > 1. Is it possible to patch it so as to disable wiki > upgrades ? Will such a change be accepted ? > I see that you've implemented this change as part of #375, and I'll take a look. > 2. Is it possible to add an option to setup Basic auth > rather than Digest ? > Is this to support functional test cases that rely on basic auth? I don't see a reason why we shouldn't have the option available. > 3. the fact that Bloodhound theme improves look and feel > in non-trivial ways has an impact on functional test cases > and helper methods . For instance , all these factors > present in recent versions have some impact on > functional test code > * there's no New Ticket link > * element IDs do not match Trac's > * there's a sort of functionalities powered by client-side > js code > * ... more TBD ... > Keep in mind that we can push changes back to the Trac test suite provided they don't harm or overcomplicate the Trac test suite. What I mean is, if there is a way to slightly change a Trac test so that it works equivalently or better for Trac and also supports Bloodhound, then I don't think we'll have any trouble pushing it to the Trac core. I'm sure this won't be true for all of the cases you are seeing though.
