https://bugzilla.wikimedia.org/show_bug.cgi?id=27877
Jure Kajzer <fr...@drajv.si> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fr...@drajv.si
--- Comment #8 from Jure Kajzer <fr...@drajv.si> 2011-05-14 08:39:12 UTC ---
I think this was the topic on IRC a while ago, but i think at that time i was
told this setup/tear-down procedure on each step was intended to provide
consistent state for each step.
So to avoid too much complication i'd suggest to create the "testing state"
tables only on first call (i.e.: if tables don't exist) and leave them there
after the completion of a test. If tables exist just truncate tables (delete
some of them as you wan't to retain initial state like user 1, interwiki, page
and user 0 for some DBbs). Finally the tables should be left there after the
parsertest finish completely as people doing these test usually 1)don't do it
on production servers 2)do it multiple times in a row if dealing with a bug. I
think it would be better to just add a parameter to parserTests main class to
just clean up testing stuff.
Parser test will usually not create that much data, so this procedure should be
faster and easier on the server resources.
Dunno ... thoughts?
--
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
