On Tue, Nov 26, 2013 at 10:29 AM, Jeff Hall <jh...@wikimedia.org> wrote:
> Quim and Željko recently brought me on board as a mentor for Google > Code-in[1], and after reviewing the QA-related tasks created so far, I came > up with an idea for a potential new task. Since I'm new to Google Code-in, > any feedback on whether or not this is an appropriate task will be > appreciated :) > > The task I'm thinking of is to start QA-relevant code convention pages as > sub-pages of the main MediaWiki coding convention page[2]. In order of > difficulty, new sub-pages to be created could be: > > > 1. Gherkin feature file conventions > > Like so? https://www.mediawiki.org/wiki/Quality_Assurance/Browser_testing/Writing_tests#Features_and_Scenarios > > 1. > 2. Cucumber (step file) conventions (see for example BZ 49876[3]) > 3. Ruby conventions (see for example GitHub Ruby StyleGuide[4]) > > > > 1. > > > The task to create a Gherkin coding convention page would require the > contributor to do a little research on what separates Scenarios from > Scenario outlines (for example), and make some preliminary recommendations > on when to prefer one over the other. > > I'd be willing to be a mentor for this task if it seems appropriate, > although I'm not sure if it's too high-level for Google Code-in. Feedback > appreciated! > > Thanks, > > Jeff > > > 1: http://www.google-melange.com/gci/homepage/google/gci2013 > 2: https://www.mediawiki.org/wiki/Manual:Coding_conventions > 3: https://bugzilla.wikimedia.org/show_bug.cgi?id=49876 > 4: https://github.com/styleguide/ruby > > _______________________________________________ > QA mailing list > QA@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/qa > >
_______________________________________________ QA mailing list QA@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/qa
