When receiving a console clear message, the webconsole should clear
the UI: remove all messages until the clear() message and close
the variables view sidebar if opened.
Add one integration tests to test console.clear calls from the content page.
MozReview-Commit-ID: GnBCBSmN1rk
--HG--
extra : rebase_source : 3bb9f99fa4ac8ed6772e325dba978ce3e6a0f202
extra : source : 671011b82100a598dd8368205bd625227bfdc060
When receiving a console clear message, the webconsole should clear
the UI: remove all messages until the clear() message and close
the variables view sidebar if opened.
Add one integration tests to test console.clear calls from the content page.
MozReview-Commit-ID: GnBCBSmN1rk
--HG--
extra : rebase_source : b26481845b5deb4213c6d25581d37e8eda3e17a7
Previously, every test and support file would be synced to the objdir
when running any test. Now that only those support files and tests requested
are synced, we note support files required beyond those in a test's
directory in ini manifests.
MozReview-Commit-ID: EmlDz9d4lqt
The problem with this test is that loadPageAndGetHud() resolves once the console
message about the request is rendered. However, the message is logged immediately
when enough info has been received instead of waiting for all updates, such as
headers, body and timings, to be received.
By the time the test calls waitForFinishedRequest(PAGE_REQUEST_PREDICATE), the
initial request is still pending and the resulting promise resolves once
the initial GET request finishes instead of the POST request triggered by
the form submission causing the test failures.
MozReview-Commit-ID: HkDdKTmzJfM
--HG--
extra : rebase_source : 3f0af6dd9e359fd440deb0c929ed6d8e04b05638
If test timings shift in the future, the unexpected requests could occur
during any test. Since there are many tests that use waitForFinishedRequest(),
any of them could start to fail intermittently at any point.
These changes fix other usages of wwaitForFinishedRequest() to include a
predicate that ignores the requests that are unexpected during the test.
MozReview-Commit-ID: Er0xyt3YBj6
The problem here is that the test expects to receive a request for the
|test-network-request.html| but the waitForFinishedRequest() accepts any
request that happens to occur at the same time. In this particular bug,
a GMP update is triggered during the test and the waitForFinishedRequest()
promise resolves with that particular request which obviously isn't the
one the test was expecting.
These changes add an optional predicate function parameter to
waitForFinishedRequest() which will be called for each completed request
and the returned promise only resolves when the predicate returns true for
a request.
Also, browser_console_netlogging.js begins to use the aforementioned
functionality by passing a predicate that only accepts the request for
|test-network-request.html| effectively fixing the intermittent failure.
MozReview-Commit-ID: AWhMRjrqP8i
