352
edits
B2G/QA/Automation/Style Guide/Python Script Style: Difference between revisions
B2G/QA/Automation/Style Guide/Python Script Style (view source)
Revision as of 21:31, 5 November 2015
, 5 November 2015→Using high-level methods: remove name
(File Headers added) |
(→Using high-level methods: remove name) |
||
| Line 120: | Line 120: | ||
* Actions should wait for the appropriate action to complete. This could be an implicit or explicit wait. For example, clicking a login button might explicitly wait for a username field to be visible. | * Actions should wait for the appropriate action to complete. This could be an implicit or explicit wait. For example, clicking a login button might explicitly wait for a username field to be visible. | ||
== Using high-level methods | == Using high-level methods == | ||
* In a test script, make sure to only have steps that are high level. Details can be encapsulated in the helper methods. | * In a test script, make sure to only have steps that are high level. Details can be encapsulated in the helper methods. | ||
* A test should remain a short entry point which leads to more details (like the main() function of a program). | * A test should remain a short entry point which leads to more details (like the main() function of a program). | ||