lp://qastaging/phantomjs

Branch merges

This import branch has no branches proposed for merge into it.

No branches dependent on this one.

Related source package recipes

1 recipe using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

1139. By Vitaliy Slobodin on 2015-10-22

Temporarily disable Ghostdriver tests on Travis CI

See issue #13667

1138. By Zack Weinberg on 2015-10-20

Don't hardwire listening ports for the test HTTP(S) servers.

Instead, run-tests.py asks the kernel to assign a random unused port
number for each, and then sets environment variables TEST_HTTP_BASE
and TEST_HTTPS_BASE to the base URLs of each server. In tests that
use testharness.js, these are exposed as global variables with the
same name; tests that don't use the harness will need to pick them out
of require('system').env if they need them. (Currently there are no
such tests.)

Part of issue #13478 (test suite overhaul).

1137. By Zack Weinberg on 2015-10-20

Add ability to test exit status and stdin/out/err directly.

This works with more //! directives at the top of a test, which
will normally be a no-harness test. It is now possible, for
instance, to test for an _unsuccessful_ exit, or for output
appearing on stderr rather than stdout. The tests for
phantom.exit and sys.stdin/out/err have been augmented
accordingly.

It is also now possible to adjust the backstop timeout on a
per-test basis, and therefore the existing timeouts have been
lowered to 5s (harness), 7s (backstop).

Part of issue #13478 (test suite overhaul).

1136. By Zack Weinberg on 2015-10-20

Reformat all individual tests' output as TAP.

This enables run-tests.py to parse it and produce structured,
pretty output. A couple of latent failures were exposed and
marked expected (having to do with control passing beyond
phantom.exit()).

TAP: http://testanything.org/tap-specification.html

Part of issue #13478 (test suite overhaul).

1135. By Zack Weinberg on 2015-10-20

Remove the old test runner.

Part of issue #13478 (test suite overhaul).

1134. By Zack Weinberg on 2015-10-20

Convert webpage-spec.js tests to the new format.

Part of issue #13478 (test suite overhaul).

1133. By Zack Weinberg on 2015-10-20

Convert non-webpage tests to the new format.

This covers fs-spec-*.js, require/require_spec.js, module_spec.js,
webkit-spec.js, and webserver-spec.js. Also, incorporate
set/690-ttf-crash/ as a regression test (it wasn't being run
automatically).

Part of issue #13478 (test suite overhaul).

1132. By Zack Weinberg on 2015-10-20

Replace assert.js with a new test harness based on W3C testharness.js.

The principal value of this test harness is its support for asynchronous
tests -- that is, tests where you have to wait for a callback to happen
before you can continue testing. This applies to every test in our
testsuite that uses WebPage.open(), and some others as well. With this
harness, the test suite is significantly faster and can be made race-free.

The API is not exactly the same as W3C testharness.js -- important
differences include: test execution is serialized within a file; "file is
test" mode has been removed, as we do not need it and it adds significant
complexity; several additional assertions have been added; the ability to
mark tests as expected to fail, or as to be skipped entirely, has been added.

New-style tests can opt out of testharness.js with a "no-harness"
directive at the top of the file; this is necessary for a small number
of tests (e.g. basics/exit.js) that test functionality the harness
reserves for its own use.

All existing new-style tests have been converted to testharness.js; some
groups of tests have been consolidated into fewer files. The naming
convention for tests in regression/ is clarified.

Part of issue #13478 (test suite overhaul).

1131. By Zack Weinberg on 2015-10-20

Overhaul run-tests.py.

 * Eliminate the global variables.
 * More thorough error detection in the HTTP(S) server.
 * Test directive comments must start with //! and the parser is more robust.
 * Handle child process stderr separately from stdout
   (this will make it possible to test more things).
 * Execute tests within each directory in alphabetical order. (#12439)
 * Support and use multi-level wildcards in TESTS. This means we don't
   have to touch run-tests.py every time we add a subdirectory to
   module/ or standards/.
 * Handle HTTP server errors during a test more gracefully. Errors caused by
   the client disconnecting in the middle of a query-response transaction are
   ignored. Other errors are reported and the test suite exits cleanly.
 * Add HTTPS and POST support to test server.
 * Add ability to run PhantomJS under a debugger on a test case.
 * Use argparse for command line parsing.
 * Accept -v as short for --verbose.
 * Repeating -v means more verbosity; at -vvv, phantomjs command lines are
   printed. (-vv is reserved for printing individual subtests, which will
   happen later.)
 * Fix bug where, with one or more -v, the pjs version number was printed
   twice.

Part of issue #13478 (test suite overhaul).

1130. By Eugeniu Ceglov <email address hidden> on 2015-09-25

Updated output message after RPM is built

Issue: #13606