One strategy
employed by Netflix is to introduce a second API layer
http://techblog.netflix.com/2012/07/embracing-differences-inside-netflix.html
on
top of the general content API to handle device-specific needs. I think
this is a sound strategy, as it contains the volatility in a
On Mon, Jan 12, 2015 at 9:31 AM, Antoine Musso hashar+...@free.fr wrote:
Hello,
I have crafted and enabled two new jobs:
* mediawiki-phpunit-hhvm
* mediawiki-phpunit-zend
...
Side effect: if one deprecates a function/method in mediawiki/core and
it is used by one of the extensions
The Wikimedia Foundation has an account with browserstack.com for
cross-browser testing. I do not think it sees much use, but in case anyone
is using the browserstack service, they had a security breach yesterday:
https://twitter.com/browserstack
Browserstack says it will publish details of the
I may be mistaken, but isn't this done by Kiwix now? There was some
discussion of that at
http://www.kiwix.org/wiki/Mediawiki_DumpHTML_extension_improvement, and
recent discussion here:
https://blog.wikimedia.org/2014/09/12/emmanuel-engelhart-inventor-of-kiwix/
I could be mistaken.
On Wed, Oct
On Tue, Sep 23, 2014 at 11:20 AM, Pine W wiki.p...@gmail.com wrote:
Sounds interesting. Will there be a video of this event, similar to the
monthly metrics meetings?
Yes, Elisabeth is agreeable, we intend to record the talk and post it if
all goes well.
-Chris
Pine
On Tue, Sep 23, 2014
On Sat, Aug 9, 2014 at 5:22 PM, dan-nl dan.entous.wikime...@gmail.com
wrote:
this is an excellent idea and i don't think it needs to be focused only on
large corporations or only on corporate individuals who want to volunteer.
i would suggest opening the idea to any developer with a skill set
On Sun, Aug 10, 2014 at 2:47 PM, Gilles Dubuc gil...@wikimedia.org wrote:
personally i really liked your comparison, when we were chatting the
other
day, to an artist in residence -- imo, programmers are the artists of our
time and this matches well.
To me the point
is to have our
On Tue, Jul 29, 2014 at 12:25 PM, Chris Steipp cste...@wikimedia.org
wrote:
On Tue, Jul 29, 2014 at 11:58 AM, Pine W wiki.p...@gmail.com wrote:
To clarify, is the QA team now under Release Engineering as Chris'
comment
seems to imply, and how does this org change effect security
On Tue, Jul 29, 2014 at 2:06 PM, Pine W wiki.p...@gmail.com wrote:
Hi Chris M.,
By the way, Wikimedians are a vocal group when there are problems, and I
take the general quiet of Wikimedia content editors about security and core
stability to mean that security and core QA are in good
in
puppet.
Would mathoid need a dedicated host?
Best
Moritz
On Mon, Jul 14, 2014 at 6:35 PM, Chris McMahon cmcma...@wikimedia.org
wrote:
I would really like to see this follow the standard deploy scheme:
implement it in beta labs; then enable it for mediawiki.org and
test2wiki;
then enable
I would really like to see this follow the standard deploy scheme:
implement it in beta labs; then enable it for mediawiki.org and test2wiki;
then enable it on production cluster nodes.
-Chris
On Mon, Jul 7, 2014 at 3:07 AM, Moritz Schubotz phy...@physikerwelt.de
wrote:
Hi,
during the last
Any logging you could add for this issue would be welcome:
https://bugzilla.wikimedia.org/show_bug.cgi?id=65709
We've been seeing it for some time, where the user is sometimes logged out
unexpectedly when using VE in beta labs. It happens a lot in automated
browser tests, and it happens to both
On Wed, Jun 25, 2014 at 4:28 PM, Tyler Romeo tylerro...@gmail.com wrote:
Therefore, I thought it may be beneficial to take that over to Wikipedia
and start our own
bug bounty program. Most likely, it would be strictly a hall of fame like
structure where
people would be recognized for
is interested in both
mediawiki core and browser tests, I'm sure the QA team would like to
get you involved.
Big thanks to hashar, Chris McMahon, and Dan Duvall for indulging me
and getting this done. I'll let them jump in with all the details I've
missed.
[1] - https://gerrit.wikimedia.org
On Fri, Jun 13, 2014 at 11:45 AM, Dan Duvall dduv...@wikimedia.org wrote:
On a related note, I'll be working on improving the mediawiki-vagrant
browser tests setup for MobileFrontend in the coming weeks. It'd be great
to have you, or someone else on the mobile team, vet the improvements.
On Thu, May 29, 2014 at 6:06 PM, Matthew Walker mwal...@wikimedia.org
wrote:
I should have also noted -- there is something strange going on with the
frontend to Special:Collection. You have to manually refresh to see status
updates...
Reported 10 days ago in test envs:
Very timely, the good people at Atomic Object have posted two articles
about what makes code untestable, I think they're good:
This Code Is Untestable! (Part 1, for Managers)
http://spin.atomicobject.com/2014/04/28/untestable-code-unit-tests/
This Code Is Untestable! (Part 2, for Developers)
On Wed, Apr 16, 2014 at 11:43 AM, Terry Chay tc...@wikimedia.org wrote:
Again, I feel a more important aspect of REST is that the interface is
extremely narrow: basically a representation of a resource (URL) and a set
of 4 CRUD commands (create read update delete = post get put delete). The
On Sat, Mar 8, 2014 at 8:05 PM, Tyler Romeo tylerro...@gmail.com wrote:
On Sat, Mar 8, 2014 at 9:48 PM, Ryan Lane rlan...@gmail.com wrote:
OK, then how did this change get deployed if it broke tests?
The problem is not that the change broke tests. The problem is that the
change broke
On Mon, Mar 10, 2014 at 10:59 AM, Tyler Romeo tylerro...@gmail.com wrote:
It's been repeated multiple times, but I'll say it again: it is disputed as
to whether account creation was broken.
It is not disputed.
When you get to the end of the account creation process and you do not have
an
http://sauceio.com/index.php/2014/03/shotsonsauce-by-jim-eisenhauer/
Now you can grab the screenshots from all the browsers and OS platforms
you want using Sauce and compare them using the little known image diff
feature on Github.
Not sure I'm going to have time to poke at this, but it seems
On Thu, Mar 6, 2014 at 8:06 PM, Gergo Tisza gti...@wikimedia.org wrote:
Hi all,
== The state of unit tests ==
We discussed these issues, and decided that writing the tests was still a
good decision at the time, but once we are done with the major code
refactorings, we should take some time
15:13, Chris McMahon cmcma...@wikimedia.org wrote:
This process is something that I think would be of great interest to a
variety of teams:
* When to throw away old tests
* When to create new tests (TDD style, before writing the code that
satisfies the test?)
* When to refactor
In over two years at WMF I have never been involved in a discussion like
this, but here goes:
In this case, I think it was entirely appropriate to revert immediately and
pick up the pieces later. The source of the code is immaterial, if Tim
Starling or Brion Vibber had merged this we would have
On Thu, Mar 6, 2014 at 4:54 PM, Tyler Romeo tylerro...@gmail.com wrote:
On Thu, Mar 6, 2014 at 6:34 PM, Brion Vibber bvib...@wikimedia.org
wrote:
Is there anything specific in the communications involved that you found
was problematic, other than a failure to include a backlink in the
On Thu, Mar 6, 2014 at 5:49 PM, OQ overlo...@gmail.com wrote:
So I'm confused on the timeline here.
Did the commit get merged before the testsuite found the breakage, or did
the commit get merged despite the testsuite failing?
The commit was merged late Wednesday. The automated tests that
On Thu, Mar 6, 2014 at 6:07 PM, OQ overlo...@gmail.com wrote:
So the testsuite only runs on merged code and not pending-merge? That
sounds like a large oversight.
Picture in your mind every branch pending merge for every extension in
gerrit. Imagine how many of those branches are eventually
On Mon, Feb 10, 2014 at 5:31 AM, Moritz Schubotz phy...@physikerwelt.dewrote:
Dear all,
recently some changes were merged to Wikipedia that broke some math
rendering for almost 2 days.
I'm highly interested to avoid that this will happen again.
On 27 January an automated test on beta labs
For anyone who might be in London at the time, this looks really
interesting: http://ticosa.org/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Thu, Nov 7, 2013 at 8:05 AM, Jon Robson jdlrob...@gmail.com wrote:
From personal experience don't touch cache manifests with a barge pole...
Bear in mind the majority of browsers provide at least 5mb of local storage
and we are talking about caching a few kB at most of minified
One thing that impressed me when I started working with WMF is that
reverting in production is as safe as I have ever seen any production
environment. In the 20 months or so I've been here, I think I only
remember one change that left behind corrupt data in prod, and that change
was made by a
On Tue, Oct 29, 2013 at 4:04 PM, Rob Lanphier ro...@wikimedia.org wrote:
Hi everyone,
I'd like to introduce Rummana Yasmeen, a new Software Test Engineer in
our QA team through April in our San Francisco office. Rummana is
going to be working with our Visual Editor team primarily on manual
On Sat, Oct 19, 2013 at 1:35 PM, Antoine Musso hashar+...@free.fr wrote:
Le 19/10/13 00:26, Erik Moeller a écrit :
Are there other ways to optimize / issues I'm missing or misrepresenting
above?
Evil plan: deploy automatically on merge. But we are not ready yet :-]
We're not ready--
On Tue, Oct 1, 2013 at 7:57 PM, George Herbert george.herb...@gmail.comwrote:
On Tue, Oct 1, 2013 at 1:34 PM, Ori Livneh o...@wikimedia.org wrote:
Foundation could play in ensuring that MediaWiki exposes the right set of
interfaces for deep integration with configuration management and
On Sat, Sep 21, 2013 at 1:21 PM, Nikolas Everett never...@wikimedia.orgwrote:
On Sat, Sep 21, 2013 at 10:26 AM, Chad innocentkil...@gmail.com wrote:
On Fri, Sep 20, 2013 at 11:47 PM, billinghurst billinghu...@gmail.com
wrote:
If you can't wait you can read the regression tests here:
When we began creating cross-browser regression tests using Selenium, we
kept them all in a repository named '/qa/browsertests'. We created
regression tests for features across all WMF development teams and Platform
functions, from the appearance of Preferences to navigating UploadWizard to
Just confirming that nothing is required for OPW and that this is only for
GSoC
-Chris
On Tue, Jul 23, 2013 at 7:00 AM, Quim Gil q...@wikimedia.org wrote:
GSoC mentors: read this email through and submit your mid-term evaluation
between 29 July - 2 August in Google Melange. One per project is
On Tue, Jul 23, 2013 at 1:42 PM, Roan Kattouw roan.katt...@gmail.comwrote:
On Tue, Jul 23, 2013 at 12:44 PM, Daniel Barrett d...@vistaprint.com
wrote:
Risker asks:
Of course those nowiki tags weren't added by the editors, VE doesn't
let you do that directly. What I think Robert was talking
On Mon, Jun 17, 2013 at 1:28 PM, S Page sp...@wikimedia.org wrote:
* enwiki says Hello dolly in quotes gives different results, mw directly
contradicts this. Even on my local wiki, quotes make a difference.
* enwiki disagrees with itself what a dash in front of a word does.
I did some
In recent times QA has expanded our automated cross-browser testing: we
re-organized our builds, pointed the tests to beta labs wikis as well as
test2wiki, and we've written a number of new tests. In the course of that
a lot of our builds for Internet Explorer versions began to fail.
I've just
forward to using YuviPanda's new github-gerrit
integration.
Again, we extend an invitation to anyone interested in testing, test
automation, and QA activities in general to join the mail list at
https://lists.wikimedia.org/mailman/listinfo/qa
-Chris McMahon
QA Lead for WMF
On Thu, May 9, 2013 at 8:13 PM, Sumana Harihareswara
suma...@wikimedia.orgwrote:
https://lwn.net/Articles/548910/
A summary of talks at a recent conference on test automation, with a
bunch of links for people who want to follow up and watch videos.
Chris McMahon was at this conference
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
On Fri, Apr 19, 2013 at 6:03 AM, Mathieu Stumpf
psychosl...@culture-libre.org wrote:
Hi,
Reading the 2012-13 Plan, I see that multimedia is one the key
activities for Mediawiki. So I was wondering if there was already any plan
to integrate 3D model viewers, which would be for example very
Over the last week Željko and I changed the QA automated browser tests to
target test environments on the beta cluster as well as on test2wiki, where
they had been running for some time.
This was possible because of a number of improvements made to beta since
the QA Quarterly Review and the f2f
On Fri, Mar 22, 2013 at 6:55 AM, K. Peachey p858sn...@gmail.com wrote:
On Fri, Mar 22, 2013 at 10:30 PM, Željko Filipin zfili...@wikimedia.org
wrote:
Most of these projects seem to be extension (and PHP?) centric. Can we
have more diversity?
Browser test automation? Not an extension,
On Tue, Mar 12, 2013 at 2:21 PM, Matthew Flaschen
mflasc...@wikimedia.orgwrote:
In the case of the GettingStarted extension v2, we used a feature branch
because it was a user-facing change that took a few weeks to get ready
for deployment. Because it was user-facing, there were interactions,
On Fri, Feb 22, 2013 at 7:06 PM, Matthew Flaschen
mflasc...@wikimedia.orgwrote:
On 02/22/2013 09:38 PM, Chad wrote:
So, I've seen this site tossed around quite a bit recently, and I'm
curious:
is there any plan to start integrating this jenkins and our other
jenkins?
Depends on what you
On Thu, Feb 21, 2013 at 2:01 PM, Tyler Romeo tylerro...@gmail.com wrote:
I'd like to see MediaWiki gain a more stable release process as well. I
think some of the primary things that we're lacking are:
- Where is QA? I mean, I know somewhere somebody is probably doing some
sort of
On Wed, Feb 13, 2013 at 6:19 AM, Petr Bena benap...@gmail.com wrote:
Okay - so what is outcome? Should we migrate beta cluster? Are we going to
use it in production?
At the risk of derailing the conversation to an unrelated subject, I would
rather work on finding a way to keep the db on beta
Links and details, along with updates as they happen, are available on the
testing page at
http://www.mediawiki.org/wiki/Article_feedback/Version_5/Testing_Feb_2013
...
The WMF Editor Engagement team has been updating the Article Feedback tool,
improving both the back end architecture and
Given the Javascript LevelUp Bootcamp sessions coming up, I thought this
would be of interest:
https://shanetomlinson.com/2013/testing-javascript-frontend-part-1-anti-patterns-and-fixes/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
Still working on details credits. Your feedback is welcome!
It would be great if you could mention browser test automation explicitly
on page 4, especially since Zeljko is giving a talk on the subject at
FOSDEM Saturday: https://fosdem.org/2013/schedule/event/testing_mediawiki/
We in QA discussed some possibilities for the browser test automation
community activities, and we suggest that the first couple of community
events be educational. In particular, we think it would be beneficial to
start with some introductory topics to be presented as a hangout+IRC
* how to read, understand and analyze results in the Jenkins system we
have
for browser automation
A good proposal, booked for the week starting on Mar 11. Please help
defining what could be the practice, the actual contribution made by
participants at the end of the week.
It's right
On Wed, Jan 16, 2013 at 3:25 PM, Quim Gil q...@wikimedia.org wrote:
All the better if there is certain correlation between testing and bugs
activities, but no problem if there is none.
I'm glad you mentioned this, it's something I'd like to bring up with
Andre and Valerie. Note that much of
Compared to the current situation, this wheel looks powerful and at the
same time relatively easy to set up. There will plenty of things to improve
and fine tune, but probably none of them will require to stop the wheel.
What do you think?
Our object here is to foster a community interested
They are ready to start. Next week.
Keep in mind that we're migrating data centers next week and all the
Wikipedias will be subject to intermittent read-only access and possibly
other issues. Hopefully we'll be stable by Thursday.
VisualEditor looks like the primary goal, having Milkshake
That is a good point. But even more important is to decide what is the
testing environment.
Thanks Isarra, I hadn't known VE was an option on enwp now, nor did I know
about
And finally, many wikis built their own custom features:
ProofreadPage on wikisource is of particular note here, e.g.
https://en.wikisource.org/w/index.php?title=Page:United_States_Statutes_at_Large_Volume_43_Part_2.djvu/15action=edit
-Chris
___
Željko Filipin, QA Engineer for WMF, will be giving a presentation at
FOSDEM in Brussels Feb 2 about our browser automation project.
Congratulations Željko, it looks like a great track to be part of.
https://fosdem.org/2013/schedule/track/testing_and_automation/
On Tue, Jan 8, 2013 at 12:58 AM, Petr Bena benap...@gmail.com wrote:
From my point of view, this is something what will be possible in future. I
thought that once we finish working on beta cluster, all deployment will be
done there, and then once it is found working, it's merged with
On Fri, Jan 4, 2013 at 10:04 AM, David Gerard dger...@gmail.com wrote:
On 4 January 2013 17:02, Mark A. Hershberger m...@everybody.org wrote:
Is anyone else interested in helping to make this happen?
I have no coding ability but would LOVE this for our work 1.19
instances, and would be
I've sorted, linked, tagged, organized, and gardened our collection of QA
pages on mw.o to be more useful. Of course there is always more to do, so
comments, criticism, edits are welcome.
http://www.mediawiki.org/wiki/QA
-Chris
___
Wikitech-l mailing
On Sat, Dec 29, 2012 at 1:47 PM, Bryan Tong Minh
bryan.tongm...@gmail.comwrote:
This is an annoyance to me as well. So, I went triaging, and finally found
the issues that failed the unit tests for me. I have committed fixes for
them to gerrit:
https://gerrit.wikimedia.org/r/#/c/41362/
Hi,
A number of people I know of have ideas and aspirations pertaining to a
DevOps-style deployment process, a.k.a Continuous Deployment. In recent
times a number of pieces of such a system have become functional: Zuul,
Jenkins enhancements for tests, automated acceptance tests, etc.
But
On Tue, Dec 18, 2012 at 11:28 AM, Mark Holmquist mtrac...@member.fsf.orgwrote:
Is there any reason why this shouldn't be a stated policy? If not,
where should we state the policy so that people are aware of it?
Considering that testwiki has a nice documentation page [0] and
test2wiki
On Tue, Dec 18, 2012 at 9:27 AM, Petr Bena benap...@gmail.com wrote:
It would be cool if part of that policy was testing on beta cluster which
is also supposed to be identicaly configured as production and is even
closer to production because the MediaWiki space is cloned from production
and
Following the process for requesting the creation of a MediaWiki group,
here is a proposal for MediaWiki Group Browser testing
http://www.mediawiki.org/wiki/Groups/Proposals/Browser_testing
This group welcomes anyone interested in the automated browser testing
project of WMF. Technical skills and
On Wed, Dec 12, 2012 at 4:06 AM, David Gerard dger...@gmail.com wrote:
There used to be Wiki Wednesdays in London - not just MediaWiki or
Wikipedia - but all sorts of wikis. Mostly corporate users. These
petered out from lack of general interest, though. It surprises me, as
I'd expect a lot
Would it be possible to enable VE on test2 in the same way? I would like
to use it in a noisy way, and would rather not make noise on enwiki.
-Chris
On Tue, Dec 11, 2012 at 8:30 PM, James Forrester
jforres...@wikimedia.orgwrote:
TL;DR: Today we are launching an alpha, opt-in version of the
On Wed, Dec 12, 2012 at 8:59 AM, Chad innocentkil...@gmail.com wrote:
On Wed, Dec 12, 2012 at 10:58 AM, Chris McMahon cmcma...@wikimedia.org
wrote:
Would it be possible to enable VE on test2 in the same way? I would like
to use it in a noisy way, and would rather not make noise on enwiki
Have a link? 'Cheap smartphone' seems a contradiction.
$50 Huawei phones running an ancient Android and only getting cheaper.
Jimbo's all about them.
http://techcrunch.com/2012/12/10/50-android-smartphones-are-disrupting-africa-much-faster-than-you-think-says-wikipedias-jimmy-wales/
This is a great outline. I am looking forward to contributing to the areas
where I have some experience and expertise, and learning about the areas
where Quim does and I don't!
-Chris
On Wed, Nov 21, 2012 at 4:45 PM, Quim Gil q...@wikimedia.org wrote:
Here is a first stab for a draft proposal
This proposal feels detached from reality. Right now features teams mostly
do one of the following, in my experience:
1). Product managers and developers do their own manual QA. For PMs this
aligns with verifying requirements, for developers it's checking their own
work. It can be a pain
QA activity days often lead to a large number of duplicate issues
being filed.
This is true. But I think there is value when new users (for some value of
new) file duplicate issues. In particular, I think it points up a
possible need to increase the severity/priority of the issues
I'll also note that ShortURL is also live on test2.wikipedia.org, and that
it seems to cause an error on every page for IE7.
On Wed, Oct 31, 2012 at 6:00 AM, Raimond Spekking
raimond.spekk...@gmail.com wrote:
Am 31.10.2012 02:48, schrieb Everton Zanella Alvarenga:
Hi,
wouldn't be nice?
Mediawiki.org please. mw.o is host to much more technical discussion than
meta.
On Wed, Oct 10, 2012 at 4:25 AM, Siebrand Mazeland (WMF)
smazel...@wikimedia.org wrote:
Hi Andre,
Can we please change the venue for this discussion? English Wikipedia
is not used and/or visited by all.
It
I'd like an excuse to get to the Front Range, though, hopefully Michelle
and I could meet face-to-face at some point. http://goo.gl/maps/6m5yz
It's been a real pleasure working with Michelle through the hiring process
and orientation, and I am looking forward to the QA staff doing some nifty
Hello everyone,
I am pleased to announce that Željko Filipin joins WMF this week as QA
Engineer.
Željko is is a world-class expert on browser test automation, software
testing, and related systems and tools. He will be leading our browser
test automation effort as well as doing other QA and
When I was hired as QA Lead almost seven months ago, WMF lacked a test
environment where
* code was routinely deployed ahead of production
* the test environment emulated the production environment closely
* aspects of the test environment (config, permissions, etc.) could be
easily and reliably
http://commons.wikimedia.beta.wmflabs.org/wiki/Special:UploadWizard
I am a bad editor.
-Chris
On Fri, Sep 28, 2012 at 9:48 AM, Chris McMahon cmcma...@wikimedia.orgwrote:
When I was hired as QA Lead almost seven months ago, WMF lacked a test
environment where
* code was routinely deployed
On Fri, Sep 28, 2012 at 11:10 AM, Arthur Richards
aricha...@wikimedia.orgwrote:
Chris, this sounds really cool. Can you point us to some specs about how
the test environment is set up (what is the architecture like, what
services are running, etc)? How closely does it emulate the production
On Fri, Sep 28, 2012 at 11:37 AM, Arthur Richards
aricha...@wikimedia.orgwrote:
This is super awesome.
This is something that could be useful for MobileFrontend, although I
suspect there will need to be some additional configuration work to mimic
how mobile requests get handled on the
On Fri, Sep 28, 2012 at 11:49 AM, Siebrand Mazeland (WMF)
smazel...@wikimedia.org wrote:
1. How can I get access to this environment, so I can fiddle with it,
too (or is this done through test puppet changes or something?
Depends on what you mean by 'access' and 'fiddle'.
Beta labs is
This crossed my desk this morning, it is a long and detailed (and honest!)
account by an insider of Google's efforts to increase code quality and
product quality. I think it's relevant to what we're doing at WMF, and
what we might do in the future.
Most software projects fail (for some definition of fail). Even for
highly skilled and highly experienced companies and shops, most software
projects fail. I'm not going to look up the Gartner and Forrester and
Chaos reports this late on a Monday night, but google away.
GSoC is an investment
On Wed, Aug 22, 2012 at 6:16 PM, Mark Holmquist mtrac...@member.fsf.orgwrote
Pi to the fifth points to Chris McMahon for being awesome in many ways,
most notably the recent EtherEditor testing he helped with.
Back atcha. Mark is cranking out a ton of code on several projects, is a
go-to guy
Once code review is complete, there'll be at least one more testing
phase, this time with specific questions, followed by a pitch by me to
Wikimedia Commons. Only after that will I even utter the d word in
the context of TranslateSvg.
Please let me know when you get here, I am really
The goal would be to lure experienced TDD devs in by focusing the event on
testing, make them work with the community during a weekend on the code
base, existing test, writing tests, etc. and mentor others along the
way. (I'm still convinced that giving it a cool, flashy, name doesn't hurt
«Testing Wikipedia» could be a nice catchy name for a series for events in
various cities around TDD, with experienced dev mentoring less experienced
community members, etc. Even if the experts come and go, everybody learn,
some test and process get done, and the community grow and learn.
As you might know, we have been making significant improvements to the beta
cluster in labs[1]. I wanted to point out two developments of the last few
days that I think are important milestones.
First, the TimedMediaHandler extension that we've been testing in the beta
commons wiki for quite
On Fri, Jul 27, 2012 at 11:29 AM, Rob Lanphier ro...@wikimedia.org wrote:
I think our best mitigation strategy is to do as good a job as we possibly
can integrating Gerrit with GitHub, combined with other improvements to
Gerrit.
One thing I don't think has been explicitly said yet, although
This is all a fantastic idea. Distributing Wikipedia in a fashion similar
to git will make it a lot easier to use in areas where Internet connections
are not so common.
I wonder could this sort of feature be implemented in the existing Kiwix
codebase? That would be ideal I think.
Ward
Christian, thanks for the information about DatabaseBase for mocking, that
makes sense.
I don't know PHP at all, but I know something about how to do automated
tests. Besides manipulating tables directly, I've seen a couple of other
things in the unit tests that struck me as strange also:
* at
P.S.: On a related note ... one could think about mocking the database
as a whole for PHPUnit tests. Thereby, one would get rid of
unnecessary database coupling for unit testing, get better
control/detection of side effects, and really solve the database
performance problem for unit tests
On Wed, Jun 27, 2012 at 2:06 PM, Derric Atzrott
datzr...@alizeepathology.com wrote:
So I hate to be that guy who doesn't know the simple things, but what is
Jenkins? The server has come up in discussion a few times since I joined
this mailing list about a month ago.
And since no one has
On the QA front, this came up in a WMF discussion recently, and I proposed
it as a Weekend Testing Americas session, but it would work equally well at
Wikimania, and it fits our goal of bringing in more community testing
nicely:
Wikipedia has a large number of open bug reports, like around
On Thu, Jun 14, 2012 at 5:21 AM, Arun Ganesh arun.plane...@gmail.comwrote:
6% of wikimedia project page views are from IE6/7 - because of the
following:
- IE6 ships default with XP
- Legal users with SP2+ can upgrade to IE8
- If you have 90s era hardware, no SP for you. Can only be solved by
Similar to last month's event with the Weekend Testing group, this Saturday
WMF is teaming with Openhatch.org for a test event to get critical
eyeballs on the near-final version of the Article Feedback Tool before AFT
gets rolled out to a wide audience in the very near future.
Like last time, we
1 - 100 of 116 matches
Mail list logo
