This has a json file which does the mapping between test cases and dependencies. Currently this is quite crude and it only distinguishes between the webapp tests that use chromedriver and all the other tests. So as the next piece of work we could try and refine the list a bit more using above approach.
Thanks for review Sergio.
I like the idea of discovering the dependencies for tests. I am also working on the next branch which provides the ability for dynamic dependencies, so you only use the dependencies you need for a specific group of tests: https:/ /code.launchpad .net/~canonical -platform- qa/ubuntu- system- tests/dynamic- dependencies/ +merge/ 299943
This has a json file which does the mapping between test cases and dependencies. Currently this is quite crude and it only distinguishes between the webapp tests that use chromedriver and all the other tests. So as the next piece of work we could try and refine the list a bit more using above approach.