bobsilverberg

(function ($, window, document, undefined) {
	"use strict";

    // WebQA Automation repositories
    var WebQARepos = ['flightdeck-selenium', 'Addon-Tests', 'Affiliates-Tests',
        'marketing-project-template', 'marketplace-tests', 'mdn-tests', 'mcom-tests',
        'moztrap-tests', 'Socorro-Tests', 'snippets-tests', 'sumo-tests', 'mozwebqa-test-template',
        'qmo-tests', 'wiki-tests'];
    var repoData = [];
	// Setup our defaults

bobsilverberg

~/Documents/gitRepos/sumo-tests[merge-redesign]$ py.test tests/desktop/ -n 4 --baseurl=http://support.allizom.org
========================================================================== test session starts ===========================================================================
platform darwin -- Python 2.6.7 -- pytest-2.2.4
gw0 [33] / gw1 [33] / gw2 [33] / gw3 [33]
scheduling tests via LoadScheduling
.............X...F..F.....F......
================================================================================ FAILURES ================================================================================
__________________________________________________________ TestKnowledgeBaseArticle.test_view_helpfulness_chart __________________________________________________________
[gw3] darwin -- Python 2.6.7 /Users/robertsilverberg/.virtualenvs/sumo-tests/bin/python
self = <tests.desktop.test_kb_article.TestKnowledgeBaseArticle instance at 0x1103c78c0>

bobsilverberg

These are snippets of py.test in action, used in a talk given at 
PyCon AU 2012 in Hobart, Tasmania. They are all relevant for 
py.test 2.2 except where specified. Where taken from open source 
projects I have listed a URL, some examples are from the py.test 
documentation, some are from my workplace.

Apart from things called test_*, these functions should probably
be in your conftest.py, although they can generally start life in
your test files.

bobsilverberg

~/Documents/gitRepos/mozmill/mutt[master*]$ mutt -b /Applications/Firefox.app testjs
Running JS Tests
TEST-START | js/utils/waitfor.js | setupModule
TEST-START | js/utils/waitfor.js | testWaitForCallback
TEST-PASS | js/utils/waitfor.js | testWaitForCallback
TEST-END | js/utils/waitfor.js | finished in 3ms
TEST-START | js/utils/pageload.js | setupModule
TEST-START | js/utils/pageload.js | testWaitForPageLoad
ERROR | Test Failure | {
  "exception": {}

bobsilverberg

ERROR | Test Failure | {
  "exception": {
    "stack": [
      "waitFor@resource://mozmill/stdlib/utils.js:279", 
      "@resource://mozmill/driver/controller.js:437", 
      "@resource://mozmill/modules/frame.js -> file:///Users/robertsilverberg/Documents/gitRepos/mozmill/mutt/mutt/tests/js/frame/httpd/testHTTPd2.js:35", 
      "@resource://mozmill/modules/frame.js:634", 
      "@resource://mozmill/modules/frame.js:704", 
      "@resource://mozmill/modules/frame.js:602", 
      "@resource://mozmill/modules/frame.js:749", 

bobsilverberg

~/Documents/gitRepos/bouncer-tests[cmd]$ py.test -n 8 --baseurl=http://download.allizom.org/
Traceback (most recent call last):
  File "/Users/robertsilverberg/.virtualenvs/bouncer-tests/bin/py.test", line 8, in <module>
    load_entry_point('pytest==2.2.4', 'console_scripts', 'py.test')()
  File "/Users/robertsilverberg/.virtualenvs/bouncer-tests/lib/python2.6/site-packages/_pytest/core.py", line 468, in main
    config = _prepareconfig(args, plugins)
  File "/Users/robertsilverberg/.virtualenvs/bouncer-tests/lib/python2.6/site-packages/_pytest/core.py", line 462, in _prepareconfig
    pluginmanager=_pluginmanager, args=args)
  File "/Users/robertsilverberg/.virtualenvs/bouncer-tests/lib/python2.6/site-packages/_pytest/core.py", line 421, in __call__
    return self._docall(methods, kwargs)

bobsilverberg

~/Documents/gitRepos/mozmill[httpd*]$ mozmill -m mutt/mutt/tests/js/tests.ini -b /Applications/Firefox.app
TEST-START | controller/native_events.js | setupModule
TEST-START | controller/native_events.js | test
TEST-PASS | controller/native_events.js | test
TEST-END | controller/native_events.js | finished in 196ms
TEST-SKIPPED | dnd_content_chrome.js | Bug 760699 - waitForElement() doesn't work anymore for lazily created elements
TEST-START | frame/httpd/testHTTPd2.js | setupModule
TEST-START | frame/httpd/testHTTPd2.js | testHttpFailure
ERROR | Test Failure | {
  "exception": {

bobsilverberg

/* This Source Code Form is subject to the terms of the Mozilla Public
 * License, v. 2.0. If a copy of the MPL was not distributed with this
 * file, You can obtain one at http://mozilla.org/MPL/2.0/. */

// Include required modules
var toolbars = require("../../../lib/toolbars");

const TEST_PAGE = "http://www.mozilla.org/en-US/about/contact";

var setupModule = function(module) {

bobsilverberg

/* This Source Code Form is subject to the terms of the Mozilla Public
 * License, v. 2.0. If a copy of the MPL was not distributed with this
 * file, You can obtain one at http://mozilla.org/MPL/2.0/. */

/**
 * @fileoverview
 * The EventsAPI The ToolbarAPI adds support for waiting for events to occur.
 *
 * @version 1.0.0
 */

bobsilverberg

~/Documents/gitRepos/marketplace-tests[sia]$ py.test -k test_that_checks_that_manifest_url_cannot_be_edited_via_basic_info_for_a_free_app
====================================================================== test session starts =======================================================================
platform darwin -- Python 2.6.7 -- pytest-2.2.4
collected 75 items 

tests/desktop/developer_hub/test_developer_hub.py F

============================================================================ FAILURES ============================================================================
_______________________________ TestDeveloperHub.test_that_checks_that_manifest_url_cannot_be_edited_via_basic_info_for_a_free_app _______________________________