Some bad news: After some experimenting last week with the mw-vagrant/puppet side of things, it quickly became clear that writing out an rspec profile with the right tags would be difficult—trying to reflect on which roles are enabled in the puppet manifest is sort of a chicken-egg problem due to the declarative nature of the puppet language.
Good news: I was able to use the MediaWiki API from within mediawiki_selenium to implement a much more environment agnostic and generally less cumbersome system. So really, the bad news isn't all that bad, just moot. https://gerrit.wikimedia.org/r/#/c/151802/ Zeljko or Chris (or Juliusz?), The patch set depends on some API-client features that haven't yet been merged, namely support for siteinfo queries and response parsing. If you get a chance, I'd love to get the review moved along so we can cut a new gem version. I've implemented (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 <[email protected]> wrote: > On Fri, Aug 1, 2014 at 1:50 AM, Dan Duvall <[email protected]> wrote: > >> * If we don't want to confuse people why some tests don't run, maybe >>> we could store the list of available tags, check for available roles >>> before running cucumber and show a message saying that 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-pants alarming color. :) >> > > +1 :) > > Željko > > -- Dan Duvall Automation Engineer Wikimedia Foundation <http://wikimediafoundation.org>
_______________________________________________ Mobile-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mobile-l
