Confirmed users
1,504
edits
TestEngineering/Web/Automation: Difference between revisions
→More Information
| Line 23: | Line 23: | ||
== More Information == | == More Information == | ||
If you would like to write some automated checks for us, you will need to be familiar with version control through GitHub, programming in Python and writing automated checks in Selenium. We recognize that volunteering is always a learning opportunity, so here are a few of our favorite resources if you need to refresh what you know or learn something new before contributing: | * If you would like to write some automated checks for us, you will need to be familiar with version control through [https://github.com/ GitHub], programming in [http://www.python.org/ Python] and writing automated checks in [http://seleniumhq.org/ Selenium]. We recognize that volunteering is always a learning opportunity, so here are a few of our favorite resources if you need to refresh what you know or learn something new before contributing: | ||
Python: Dive into Python | |||
GitHub: ProGit | ** [http://www.diveintopython.net/ Python: Dive into Python] | ||
A brief introduction to POM from the Selenium site. | ** [http://progit.org/book/ GitHub: ProGit] | ||
SeleniumHQ Documentation | ** [http://code.google.com/p/selenium/wiki/PageObjects A brief introduction to POM from the Selenium site.] | ||
The difference between tests and checks | ** [http://seleniumhq.org/docs/ SeleniumHQ Documentation] | ||
As you begin writing checks, please adhere as closely as possible to the Style Guide, so we’re all on the same page, and reviews go more smoothly. Once you’ve written your tests and submitted a GitHub pull request, they will go through our Code Review process. | ** [http://www.developsense.com/blog/2009/08/testing-vs-checking/ The difference between tests and checks] | ||
File bugs to help us improve the product (Learn how to file bugs here). | |||
Each project's GitHub repository has a README.md that will you help you set up an environment and get tests running for that particular project. | * As you begin writing checks, please adhere as closely as possible to the [https://wiki.mozilla.org/QA/Execution/Web_Testing/Docs/Automation/StyleGuide Style Guide], so we’re all on the same page, and reviews go more smoothly. Once you’ve written your tests and submitted a GitHub pull request, they will go through our [https://wiki.mozilla.org/Web_Testing/Automation/CodeReviewProcess Code Review process]. | ||
* File bugs to help us improve the product (Learn how to file bugs [https://developer.mozilla.org/en/bug_writing_guidelines here]). | |||
* Each project's GitHub repository has a README.md that will you help you set up an environment and get tests running for that particular project. | |||
Our tests use the page object model: | Our tests use the page object model: | ||
If you are interested in the pre-POM Python checks we have pages that discuss the libraries and configuration files shared by the checks. | * If you are interested in the pre-POM Python checks we have pages that discuss [https://wiki.mozilla.org/QA/Execution/Web_Testing/Docs/Automation/Testcases/SharedLibraries the libraries] and [https://wiki.mozilla.org/QA/Execution/Web_Testing/Docs/Automation/Testcases/ConfigFiles configuration files] shared by the checks. | ||
| Line 107: | Line 109: | ||
Homepage: reps.mozilla.org | Homepage: reps.mozilla.org | ||
GitHub Repository: https://github.com/mozilla/remo-tests | GitHub Repository: https://github.com/mozilla/remo-tests | ||
== Documentation == | == Documentation == | ||