calling the test dictionary from the constructor is effectively
authorLuke Kenneth Casson Leighton <lkcl@lkcl.net>
Fri, 24 Jul 2020 13:33:08 +0000 (14:33 +0100)
committerLuke Kenneth Casson Leighton <lkcl@lkcl.net>
Fri, 24 Jul 2020 13:33:08 +0000 (14:33 +0100)
commiteb0d559434ae711b98e7eb4c781751a0f4d7de40
tree525156c4aa760881b20f786a3d7ef5f6ef7203dc
parent3f2a2628a6721a718ee01b9c2c27bff55feb3176
calling the test dictionary from the constructor is effectively
what unittest does.  this results in multiple copies of the test
being called (once by the dictionary-loop, once by unittest infrastructure)

getting the name of the actual test is a good thing.  used inspect.stack()
to find the name of the calling test
src/soc/fu/div/test/test_all_pipe_caller.py
src/soc/fu/div/test/test_pipe_caller.py