n't resist ... in all seriousness we could figure out a way to
generalize CI-type MW setup as libraries/tools.)
[1] https://www.mediawiki.org/wiki/Continuous_integration/Browser_tests
--
Dan Duvall
Automation Engineer
Wikimedia Foundation <http://wikimediafoundation.org>
_
ricator.wikimedia.org/T62116
>> >
>> >
>> >
>> > --
>> > Rob Moen
>> > Wikimedia Foundation
>> > rm...@wikimedia.org
>>
>> > ___
>> > Mobile-l mailing list
>> >
//gerrit.wikimedia.org/r/#/q/reviewer:jdlrobson%252Bbarry%2540gmail.com+status:open,n,z
> >>> [2] https://gerrit.wikimedia.org/r/#/c/218731/
> >>>
> >>> ___
> >>> Mobile-l mailing list
> >>> Mobile-l@lists.wikimedia.org
> >>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> ___
> >>> Mobile-l mailing list
> >>> Mobile-l@lists.wikimedia.org
> >>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >>
> >>
> >>
> >> ___
> >> Mobile-l mailing list
> >> Mobile-l@lists.wikimedia.org
> >> https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >>
> >
> >
> > ___
> > Mobile-l mailing list
> > Mobile-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >
>
>
>
> --
> Jon Robson
> * http://jonrobson.me.uk
> * https://www.facebook.com/jonrobson
> * @rakugojon
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
--
Dan Duvall
Automation Engineer
Wikimedia Foundation <http://wikimediafoundation.org>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l
want to put it :).
>
>
> I would go further and stipulate that clean coding principles apply just as
> much (if not more) to tests as they do to "production" code. Namely: don't
> repeat yourself and make the intent as clear as possible. Matching
> frameworks hel
;>> Wikimedia Foundation
>>>
>>> ___
>>> Mobile-l mailing list
>>> Mobile-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>>
>>
>>
>> __
https://phabricator.wikimedia.org/T94472
On Mon, Mar 30, 2015 at 12:39 PM, Dan Duvall wrote:
> On Mon, Mar 30, 2015 at 10:30 AM, Jon Robson wrote:
>> It really saddens me how very few engineers seem to care about browser
>> tests. Our browser tests are failing all over the pl
to writing/running browser tests?
(test framework, documentation/examples, execution time, CI)
- What are the largest barriers to debugging test failure? (test
framework, confusing errors/stack traces, documentation/examples,
debugging tools)
I'll c
/ci/view/Mobile/job/browsertests-MobileFrontend-SmokeTests-linux-chrome-sauce/
>
Have you tried to reproduce these failures by executing the tests
locally, against either Beta or your local MW? I'll be in the office
tomorrow if you want advice on how to best go about it.
Dan
from
>> an
>> > engineering standpoint, but aren't quite ready for release yet. These
>> > features often block production releases.
>> >
>> > As product owner, pushing out regular bug fix builds would make me very
>> > happy! But there is a re
to be more
portable/isolated/deterministic.
Also, I have to say that delving into these repos has been a great
on-boarding experience for me. What better way to learn about the core
features of MediaWiki than to be tasked with verifying the specs? So, thank
you!
--
Dan Duvall
Automation Engineer
W
s
On Thu, Aug 14, 2014 at 12:51 PM, Juliusz Gonera
wrote:
> Dan Duvall and I worked on his patch refactoring MobileFrontend
> browser tests yesterday [1]. We got over half of the tests working on
> mediawiki-vagrant, but we might have caused some breakage on
> betalabs/jenkins. The las
g extensions" in the stats at the end and
leaving the details inline?
On Wed, Aug 6, 2014 at 9:33 AM, Željko Filipin
wrote:
> On Tue, Aug 5, 2014 at 2:38 AM, Dan Duvall wrote:
>
>> https://gerrit.wikimedia.org/r/#/c/151802/
>> (...)
>> https://gerrit.wikimedia.org/r/
Example output:
https://wikitech.wikimedia.org/wiki/File:Screen_Shot_2014-08-04_at_5.57.13_PM.png
Does the warning seem clear and prominent enough?
On Mon, Aug 4, 2014 at 5:38 PM, Dan Duvall wrote:
> Some bad news: After some experimenting last week with the
> mw-vagrant/puppet side of
plemented (currently passing) specs for the feature, so
it seems good to go, but I wanted to get some additional eyes on it before
doing a new release.
https://gerrit.wikimedia.org/r/#/c/150977/
Thanks!
On Mon, Aug 4, 2014 at 6:06 AM, Željko Filipin
wrote:
> On Fri, Aug 1, 2014 at 1:5
hat tests requiring
> following (disabled) roles, will not run?
>
Zeljko brought this up as well. We can probably implement some sort of
after or exit hook to inform the user why some tests were skipped—based on
the invocation maybe—and output it in yellow or some other alarming but not
shit-your-
9:22 PM, Max Semenik
> wrote:
>
>> I personally would prefer 2, because buncing everything into one role
>> would be too inflexible. I don't see much maintenance overhead if compared
>> with 1.
>>
>>
>> On Fri, Jul 18, 2014 at 6:19 PM, Juliusz Goner
hrome and Firefox enwiki BetaLabs,
> and the Firefox test2 Prod projects. They now only send to qa-alerts and
> Chris McMahon.
>
> HTH!
>
> J.
> --
> James D. Forrester
> Product Manager, Editing
> Wikimedia Foundation, Inc.
>
> jforres...@wikimedia.
e mw-vagrant environment to be helpful. For things still mysterious,
I can always take notes and lean on Zeljko for answers. :)
Dan
--
Dan Duvall
Automation Engineer
Wikimedia Foundation <http://wikimediafoundation.org>
___
Mobile-l mai
18 matches
Mail list logo
