Hi, team!
Let me please present ideas collected during the unit tests improvement
meeting:
1) Rename class ``Environment`` to something more descriptive
2) Remove hardcoded self.clusters[0], e.t.c from ``Environment``. Let's
use parameters instead
3) run_tests.sh should invoke alternate syncdb() for cases where we
don't need to test migration procedure, i.e. create_db_schema()
4) Consider usage of custom fixture provider. The main functionality
should combine loading from YAML/JSON source and support fixture inheritance
5) The project needs in a document(policy) which describes:
- Tests creation technique;
- Test categorization (integration/unit) and approaches of testing
different code base
-
6) Review the tests and refactor unit tests as described in the test policy
7) Mimic Nailgun module structure in unit tests
8) Explore Swagger tool <http://swagger.io/>
--
Sincerely yours,
Ivan Kliuk
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
