mahara-contributors team mailing list archive

[Mahara Bot <1583435@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/6553
Committed: https://git.mahara.org/mahara/mahara/commit/5bcf99ec27c0f04fececfc14fa29566c8b2743af
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch:    15.10_STABLE

commit 5bcf99ec27c0f04fececfc14fa29566c8b2743af
Author: Aaron Wells <aaronw@xxxxxxxxxxxxxxx>
Date:   Thu May 19 17:22:47 2016 +1200

Bug 1583435: Let mahara_behat.sh run just one particular feature file

Change-Id: Id5c9a279f257db8c2bc832ff0799682027f62518
behatnotneeded: Covered by existing tests
(cherry picked from commit b4bcce0b9b6e71359d28102f115d62757d270e87)

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1583435

Title:
  Make it easier to run one specific feature file

Status in Mahara:
  Fix Committed
Status in Mahara 15.04 series:
  In Progress
Status in Mahara 15.10 series:
  Fix Committed
Status in Mahara 16.04 series:
  Fix Committed
Status in Mahara 16.10 series:
  Fix Committed

Bug description:
  Currently if automated tests fail and I want to re-run just one
  specific feature file, I have to manually edit the file, add "@debug"
  to it, and then tell our mahara_behat.sh script to look for that
  @debug tag. This is kind of annoying, and there's a tendency to
  accidentally leave those @debug tags there when committing.

  There's an easier way! The underlying behat command script,
  external/vendor/bin/behat, will accept a filename and only run the
  tests under that file. We can adapt our utility script to use that
  *or* a tag.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1583435/+subscriptions