Correctly persist checklist settings. - #465
Conversation
Incidentally, fixes an acceptance test (which would have caught this bug) not running. Its step regex was "They are correctly selected after I reload the page$", which happens to be matched by "I reload the page$", another step definition. Lettuce seems to arbitrarily pick between definitions if they both match a step, so it's good to ensure that each step isn't a sub-regexes of another.
|
👍 To get this into today's release candidate. However, I think this whole thing about saving before updating metadata is very confusing. @dmitchell said that there is a backlog task to remove this 2 (or 3?) step process, and I am 100% in favor of that. Also flagging @cpennington so that he is aware of the fallout. |
|
Also, the point about Lettuce matching regexp statements is a good one. I will generally avoid regexp definitions from now on, as they seem risky. |
|
A more robust short-term solution would be to have own_metadata(foo) call On Mon, Jul 22, 2013 at 3:25 PM, Christina Roberts <notifications@github.com
|
Correctly persist checklist settings.
moving all requirements that use a repo to repo-requirements.txt includi...
Hash update: Group Project V2
…-microsite-test Fix broken test from "ACCOUNT_NAME" removal
refactor(eliteu-payments): eliteu-payments plugin installation
Co-Authored-By: Omar Al-Ithawi <i@omardo.com>
Removed edx links and changed deletion text
This component blocks access to graded units when the user is required to sign the integrity agreement for the course. Once signed, it will not appear for the course again.
Incidentally, fixes an acceptance test (which would have caught this
bug) not running. Its step regex was "They are correctly selected
after I reload the page$", which happens to be matched by "I reload
the page$", another step definition. Lettuce seems to arbitrarily pick
between definitions if they both match a step, so it's good to ensure
that each step isn't a sub-regex of another.