Hi all, When I started to work on tests for WebRTC and WebAPI lately I have noticed that there are no clear specifications where tests have to be added. Some are located in a tests subdirectory (like /dom/feature/tests/) while others are under a testing folder (like /dom/testing/mochitest). This is totally confusing and as an internal discussion in the automation and tools team has been shown, we would support a location of tests which are under the feature which means directly beneath the actual source.
The proposal would be the following hierarchy: |-- feature/ |-- tests/ |-- browser-chrome/ |-- chrome/ |-- crashtests/ |-- marionette/ |-- mochitests/ |-- reftests/ |-- xpcshell |-- [..]/ So tests for each type of test framework will get their own subfolder under tests. That will make it easier for everyone to get started and we can retain a clear structure of our tests. With this post we want to get feedback from module owners and how they feel with such a reorganization of the tests. If we agree all on it I would like to go ahead and submit patches in smaller chunks most likely on a per module basis. I know that will be a lot of work, so I will do it beside my actual work and try to get as many contributors as possible to helping out via mentored bugs. Once agreed on our team will also add proper documentation on MDN as part of our current documentation revamp project for test frameworks. Thanks a lot, -- Henrik Skupin Software Engineer in Test Mozilla Corporation -- Henrik _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform