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:21, 5 November 2015
, 5 November 2015→Using high-level methods: added
(→Use testvars.json: remove dup) |
(→Using high-level methods: added) |
||
| Line 87: | Line 87: | ||
== Using high-level methods <jlorenzo>== | == Using high-level methods <jlorenzo>== | ||
* 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). | |||
* Don't detail every single tap and wait, in the test. Use methods that reflect a user's intent rather than a sequence of small steps the user has to do. The details of how to fulfill that intent will be in the page classes. | |||
<source python> | <source python> | ||
# good | # good | ||