> Doing load_tests = load_tests_from_scenarios (perhaps it would be better to
> say 'load_tests_apply_scenarios', but - *blue*) is pretty pithy, explicit and
> not terrible.
>
> Doing a global is fine to - you could simply use generate_scenarios in
> bzrlib.test_suite()
>
>
> 381 + # XXX: this is strange; the 'random' name below seems
> undefined and
> 382 + # yet the tests pass -- mbp 2010-10-11
> 383 + raise AssertionError()
>
> Looks like you can't land it like this?
I can; the bug (bug 658773) was latent before I came here, and I just noticed it by running pyflakes.
>
> This looks lovely. I would love to see a patch with the missing bits put into
> testscenarios.
> load_tests is in python 2.7 (with a slightly different signature); it would be
> nice to adapt to that.
Right, bug 607412.
> Doing load_tests = load_tests_ from_scenarios (perhaps it would be better to apply_scenarios ', but - *blue*) is pretty pithy, explicit and
> say 'load_tests_
> not terrible.
>
> Doing a global is fine to - you could simply use generate_scenarios in
> bzrlib.test_suite()
>
>
> 381 + # XXX: this is strange; the 'random' name below seems
> undefined and
> 382 + # yet the tests pass -- mbp 2010-10-11
> 383 + raise AssertionError()
>
> Looks like you can't land it like this?
I can; the bug (bug 658773) was latent before I came here, and I just noticed it by running pyflakes.
>
> This looks lovely. I would love to see a patch with the missing bits put into
> testscenarios.
Right, I'll do that under bug 658044.