Hi Jason,

It looks very good, just a few comments about minor issues:

• The commit message should include the MDLQA number
• Is there a reason to begin the test being logged as admin and then logging out, and switching to teacher? For what I see all can be done using a teacher account, also note that the background section is useful to specify the common parts of the scenarios and both of the scenarios are beginning with the same 2 steps
• https://github.com/phalacee/moodle/compare/34fb354...MDL-42285-master#diff-f8585b50cdd78933554ce41ef97bdf21R3 The description of the feature could be more informative; will extract reports from those feature files in future we will publish those reports so is good that the info about the feature is more explicative, the In order to should contain a sentence explaining why do we want this feature (http://docs.moodle.org/dev/Acceptance_testing#Writing_features) something like In order to get rid of unused or outdated questions
• Please replace https://github.com/phalacee/moodle/compare/34fb354...MDL-42285-master#diff-f8585b50cdd78933554ce41ef97bdf21R43 and other references to this step for And I click on "Add to quiz" "link" in the "Test question name" "table_row" we are deprecating this step, we are waiting for the policy to mark the deprecated steps in some way

(Editing adding more points)

• If I'm not missing something you can reference the checkbox by it's label https://github.com/phalacee/moodle/compare/34fb354...MDL-42285-master#diff-f8585b50cdd78933554ce41ef97bdf21R49
• The Then section begins in the first assertion (https://github.com/phalacee/moodle/compare/34fb354...MDL-42285-master#diff-f8585b50cdd78933554ce41ef97bdf21R48)

• Will add that
• No reason for doing it as admin, other than the edit question test I copied from did it that way. Will fix that.
• Will fix that
• Not sure what you mean there, can you please elaborate?

• I thought we were to aim to avoid using strings based on language where possible, as they are capable of changing more frequently?
• Not sure what you mean there, can you please elaborate?

#4, we will deprecate And I click on "Add to quiz" "link" in the "Test question name" table row but is not marked as deprecated ATM, would be good if you use And I click on "Add to quiz" "link" in the "Test question name" "table_row" instead, otherwise we will change them along with the other I click on "Add to quiz" "link" in the "Test question name" table row uses, is not critical

#5, yes, they are changing, but is more important that the tests are readable, as you have been doing during the whole test but this specific step. What we must do is use get_string() calls when we are working on step definitions (php)

#6, np, this seems to be the most asked/answered question The scenarios are split in 3 parts, the Given, When and Then prefixes are used to split it, you can read a scenario and with a quick sight see what it is testing according to those prefixes. Given to set the initial context, When when performing an action that provokes a change in the system (the change we are testing) and Then to check the outcomes of that action. Most of the time a scenario is not just testing one action, but all counts as checking outcomes from the first outcomes checking (https://github.com/phalacee/moodle/compare/34fb354...MDL-42285-master#diff-f8585b50cdd78933554ce41ef97bdf21R4 -> we should use Then)

Okay, that should be it all fixed. Can you please just check it one last time, then I will backport it and write some instructions for it?

All good Jason, thanks

The main moodle.git repository has just been updated with latest weekly modifications. You may wish to rebase your PULL branches to simplify history and avoid any possible merge conflicts. This would also make integrator's life easier next week.

TIA and ciao

EDIT: sorry - my bad!

you need a config for your own behat environment in there Dan

Integrated, thanks

Works for me, thanks

FYI: related MDLQA-93 has been moved from MDLQA-1 to MDLQA-5249 (bag of behat-converted tests). Thanks!

Sweet, one less thing we have to repeat manually every six months.

Congratulations - this issue has been included in Moodle and is now available on our git mirrors and shortly will become available on the download servers shortly.