I used the metaclass to detect a developer forgetting to add their new test
file to the list, but discovery would be better.


On Mon, Aug 26, 2013 at 5:03 PM, James Bergstra <james.bergstra@gmail.com>wrote:

> Hmm, yes discovery is what I want here, I didn't think of that. You're
> right that what I want to do is call discovery on the nengo module to
> collect tests for nengo_ocl.
>
>
> On Mon, Aug 26, 2013 at 4:32 PM, Trevor Bekolay <notifications@github.com>wrote:
>
>> In nengo/tests/list_of_test_modules.py:
>>
>> > @@ -0,0 +1,12 @@
>> > +# -- import these modules to populate the registry
>> > +#    of standard simulator test cases
>> > +#    `helpers.simulator_test_cases`
>> > +simulator_test_case_mods = [
>> > +    'nengo.tests.test_circularconv',
>> > +    'nengo.tests.test_ensemble',
>> > +    'nengo.tests.test_model',
>> > +    'nengo.tests.test_node',
>> > +    'nengo.tests.test_old_api',
>> > +    'nengo.tests.test_simulator',
>> > +    ]
>> > +
>>
>> It's super easy to forget to add your test module to this list. Isn't
>> this what discovery<http://docs.python.org/2/library/unittest.html#test-discovery>is for?
>>
>> —
>> Reply to this email directly or view it on GitHub<https://github.com/ctn-waterloo/nengo/pull/72/files#r5988772>
>> .
>>
>
>