Hello - We use fixtures extensively, but recently came across a problem where we had to run parallel tests using the nose multi-process plugin. We have a lot of tests that rely on fixtures, and our tests take time and we want to optimize the run. Apparently, with the way fixtures are designed, this is hard because the loadable DataSet is a singleton. The workaround is to create a dataset per test, which is impractical and unmaintainable and defeats the entire purpose.
One option is to allow passing inner classes to the Superset class or to the SQLAlchemyFixture class. Please suggest alternatives.
Hello - We use fixtures extensively, but recently came across a problem where we had to run parallel tests using the nose multi-process plugin. We have a lot of tests that rely on fixtures, and our tests take time and we want to optimize the run. Apparently, with the way fixtures are designed, this is hard because the loadable DataSet is a singleton. The workaround is to create a dataset per test, which is impractical and unmaintainable and defeats the entire purpose.
One option is to allow passing inner classes to the Superset class or to the SQLAlchemyFixture class. Please suggest alternatives.