(In reply to Julian Descottes [:jdescottes] from comment #9) > Quick question about documenting those tests. At the moment we are still going to modify the tests a lot, some of them might be converted to regular mochitests with asserts, some might be deleted, renamed etc... So there is going to be a good amount of changes. > > Could you explain a bit how this documentation is used by sheriffs (taking into consideration that DevTools alerts are sheriffed by our team) ? Any way we could consider the non-documented tests as experimental? I have the task to provide links to the DevTools documentation in Perfherder and this is mainly to help your team access the docs easily while sheriffing. There are two options I think, either I do not provide a link for what's left undocumented, either you can add only the title of the tests in Perfdocs and some description "To be defined" (here's an example https://firefox-source-docs.mozilla.org/testing/perfdocs/awsy.html#base-content-resident-unique-memory).
Bug 1723719 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Julian Descottes [:jdescottes] from comment #9) > Quick question about documenting those tests. At the moment we are still going to modify the tests a lot, some of them might be converted to regular mochitests with asserts, some might be deleted, renamed etc... So there is going to be a good amount of changes. > > Could you explain a bit how this documentation is used by sheriffs (taking into consideration that DevTools alerts are sheriffed by our team) ? Any way we could consider the non-documented tests as experimental? I have the task to provide links to the DevTools documentation in Perfherder and this is mainly to help your team access the docs easily while sheriffing. There are two options I think, either I do not provide a link for what's left undocumented, either you can add only the title of the tests in Perfdocs and some description "To be defined" (here's an example https://firefox-source-docs.mozilla.org/testing/perfdocs/awsy.html#base-content-resident-unique-memory). Please let me know which approach suits this situation the best. Thanks.