On Tue, Apr 30, 2013 at 11:31 AM, Matthew Flaschen
<mflaschen(a)wikimedia.org>wrote;wrote:
On 04/30/2013 08:25 AM, Indrani Sen wrote:
Scope: To do functionality testing of selected
features(i.e
Print/Export PDF option etc. ) of the website on selected browser(i.e
IE, FF, Chrome etc.) This is nothing to do with Performance Testing,
Load Testing of the website.
Thank you for your proposal. I think the scope should be more specific.
There are of course a vast number of MediaWiki features, including many
in extensions. Some of these already have browser tests. Many do not.
And quite a number of ongoing projects have no need of browser tests
Your proposal should try to give a clear idea of what
tests (which
extensions, which parts of MediaWiki core, etc.) you will work on.
Also, any constraints or obstacles that you might encounter in the course
of such tests. For example, you mention exporting PDFs. This requires
access not only to the browsers, but also to the underlying file system,
which changes according to where the test is run (Windows, Linux, Mac, FAT,
ext3, etc.). We have solved this problem for testing UploadWizard in
multiple browsers, and work on exporting PDFs is already beginning.
You mention test data. Where will this test data reside? Again, we have
in place a somewhat complex arrangement of shared public test environments
right now. How does your proposal fit in?
Have you seen our reporting in Jenkins that we have in place already?
-Chris