B2G/QA/Automation/Style Guide: Difference between revisions
< B2G | QA | Automation
Jump to navigation
Jump to search
No edit summary |
(Added disclaimer about the differences across the code base) |
||
| Line 3: | Line 3: | ||
<br> | <br> | ||
<br> | <br> | ||
== General disclaimer == | |||
As we develop more knowledge some tests might fall behind the standards in this style guide. It can be tempting to want to fix all of the outdated style but in order to keep patches/pulls small (see above!) we are happy to have new and old standards of code sit side by side. As we regularly review and update tests the project will be brought completely up to our current standards. | |||
Or if you prefer, file a [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox%20OS&component=Gaia%3A%3AUI%20Tests Bugzilla issue] to have a section of code addressed separately to the job you are doing. | |||
== [[B2G/QA/Automation/Style Guide/General Concepts|General Concepts]] == | == [[B2G/QA/Automation/Style Guide/General Concepts|General Concepts]] == | ||
== [[B2G/QA/Automation/Style Guide/Howtos| How-Tos ]] == | == [[B2G/QA/Automation/Style Guide/Howtos| How-Tos ]] == | ||
Revision as of 15:50, 10 November 2015
The goal of this style guide is to provide rules to write ui-automation code that is clear and effective.
It is a fork of this webqa page.
General disclaimer
As we develop more knowledge some tests might fall behind the standards in this style guide. It can be tempting to want to fix all of the outdated style but in order to keep patches/pulls small (see above!) we are happy to have new and old standards of code sit side by side. As we regularly review and update tests the project will be brought completely up to our current standards.
Or if you prefer, file a Bugzilla issue to have a section of code addressed separately to the job you are doing.