On Thu, 23 Sep 2010 09:24:18 -0700, Brion Vibber wrote:
Given a test matrix with multiple OSes, this ain't something individual devs will be running in full over and over as they work. Assume automated batch runs, which can be distributed over as many databases and clients as you like.
For small test subsets that are being used during testing the equation still doesn't change much: reset the wiki to known state, run the tests. Keep it simple!
-- brion
On Thursday, September 23, 2010, Dan Nessett dnessett@yahoo.com wrote:
On Wed, 22 Sep 2010 12:30:35 -0700, Brion Vibber wrote:
On Wed, Sep 22, 2010 at 11:09 AM, Dan Nessett dnessett@yahoo.com wrote:
Some have mentioned the possibility of using the wiki family logic to help achieve these objectives. Do you have any thoughts on this? If you think it is a good idea, how do we find out more about it?
I'd just treat it same as any other wiki. Whether you're running one or multiple wiki instances out of one copy of the code base, it just doesn't make a difference here.
-- brion
Not to hammer this point to hard, but there is another reason for supporting switching in of temporary resources.
We have one worked example of a Selenium test - PagedTiffHandler. During the course of its execution, it uploads some tiff files to test some of its functionality. Currently, once an image is uploded, there is no way to completely delete it (short of drastic administrative action involving raw database manipulation). So, running PagedTiffHandler twice doesn't work unless you switch in temporary resources on each run that are then deleted at the end of the run.
-- -- Dan Nessett
_______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
I am very much in favor of keeping it simple. I think the issue is whether we will support more than one regression test (or individual test associated with a regression test) running concurrently on the same test wiki. If not, then I agree, no switching logic is necessary.