TestEngineering/Performance/NewContributors: Difference between revisions

TestEngineering/Performance/NewContributors (view source)

149 bytes added , 14 February 2020

Link to onboarding review section.

97

edits

@@ Line 29: / Line 29: @@
 == Work on bugs and get code review ==
-Once you are familiar with the code of the test harnesses, and the tests you might want to start with your first contribution. You can follow [https://firefox-source-docs.mozilla.org/contributing/how_to_contribute_firefox.html#to-write-a-patch these instructions] on how to submit a patch.
+Once you are familiar with the code of the test harnesses, and the tests you might want to start with your first contribution. You can follow [https://firefox-source-docs.mozilla.org/contributing/how_to_contribute_firefox.html#to-write-a-patch these instructions] on how to submit a patch. You can find review instructions that are specific to the team [https://wiki.mozilla.org/TestEngineering/Performance/Onboarding#Review_policy here].
 How you test a patch will change depending on what's being modified. Generally, you will be running Raptor-webext (with commands similar to those listed above) or it's unit-tests to test your changes, but you can ask us in [https://chat.mozilla.org/#/room/#perftest:mozilla.org #perftest] if you're not sure what you should run or if you need help getting a test command working. For the patch reviewer, you can use <tt>#perftest</tt> and someone from the team will review it (or you can put whoever helped you with the patch).