QA/Execution/Web Testing/Automation tools: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 30: Line 30:
** More support from WebQA
** More support from WebQA
** More options for testing using pytest
** More options for testing using pytest
== Load Testing ==
* [https://github.com/mostlygeek/beeswithmachineguns Bees with Machine Guns]
** Forked improved version, rather than original
** https://irccloud.mozilla.com/pastebin/RjGUbTDs/.boto
* Locust


==Headless testing==
==Headless testing==

Revision as of 16:36, 12 August 2015

List of Automation tools

Evaluations of current Automation tools, languages, tools for continuous delivery.

Big picture questions:

  • When do you get a new framework or language?
  • When is it time to move away from how things have been done?
  • Risk of complexity and instability of going with new tools vs. Risk of irrelevancy and being left out of the process

Continuous Integration

  • Jenkins
    • Open to all contributors
    • Considered to be outside of the project development release process
  • Travis CI

Data collection tools

  • Datadog
  • Google Analytics

Site Monitoring tools

  • New Relic

Languages

  • JS
    • More support from developers who prefer the language
    • Async testing framework
    • Scripts vs. Page Objects
  • Python
    • More support from WebQA
    • More options for testing using pytest

Load Testing

  • Locust

Headless testing

  • Are page renderings being tested?
  • What approximation to a "real" browser do these frameworks represent?
  • Are these proper
  • Value of running speed

Casper.js

  • Opinion: Easy to learn and set up, simple API

Phantom.js

Slimer.js

Webdriver/Selenium

Intern.io

  • Opinion: Verbose API

Webdriver JS framework

  • Opinion: better than Intern, not as complete as Selenium/Python