Re: [Wikitech-l] OPW Browser Test Automation - Proposal Summary
On Tue, Apr 30, 2013 at 2:25 PM, Indrani Sen i@se12.qmul.ac.uk wrote: I am summarizing here my proposal idea for OPW MediaWiki projects. I have noticed that you did not provide the link to your proposal[1]. In addition to the comments that I have posted here, I have left a few comments on the talk page[2]. Željko -- 1: http://www.mediawiki.org/wiki/User:Indranisen 2: http://www.mediawiki.org/wiki/User_talk:Indranisen ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] OPW Browser Test Automation - Proposal Summary
Hi Indrani, We already have an ongoing browser test automation project[1]. For a quick overview take a look at the first 14 minutes of tech talk from 28 February[2]. Other comments are inline. On Tue, Apr 30, 2013 at 2:25 PM, Indrani Sen i@se12.qmul.ac.uk wrote: Tools : Test Automation testing tool to be used - Selenium suite or Cucumber. We actually already use both. Test Cases to be maintained in spreadsheet or any version controlled tools. We would probably have to discuss what you mean by test case but we use Cucumber for that. Take a look at any file in features[3] folder: Test Report to be prepared in graphical format, any open source tool can be used. We use Jenkins. For an example take a look at browsertests-en.wikipedia.org-linux-chrome[4] job. If you have any questions, please let me know. Željko -- 1: https://github.com/wikimedia/qa-browsertests/ 2: http://youtu.be/3UPDzPBf4t8 3: https://github.com/wikimedia/qa-browsertests/tree/master/features 4: https://wmf.ci.cloudbees.com/job/browsertests-en.wikipedia.org-linux-chrome/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] OPW Browser Test Automation - Proposal Summary
On 04/30/2013 08:25 AM, Indrani Sen wrote: Hello, I am summarizing here my proposal idea for OPW MediaWiki projects. Objective: To test MediaWiki/WikiPedia websites across different browsers. To make sure various website features are supported on different browser platforms. This is mainly functionality testing of website features. When a new feautre is implemented, regression testing to be done to make sure existing feaures work fine. Once the tests are passed, it can be confirmed that the tested feature support the particular browsers. 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. Your proposal should try to give a clear idea of what tests (which extensions, which parts of MediaWiki core, etc.) you will work on. Matt Flaschen ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] OPW Browser Test Automation - Proposal Summary
On Tue, Apr 30, 2013 at 11:31 AM, Matthew Flaschen mflasc...@wikimedia.orgwrote: 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 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
