Closed
Bug 1449184
Opened 8 years ago
Closed 8 years ago
Add support for raptor test timeouts
Categories
(Testing :: Raptor, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rwood, Assigned: rwood)
References
Details
Attachments
(1 file)
Need timeout logic to handle when test pages don't load (i.e. 404) or when the page loads but not all measurements are received.
Have a default timeout value but allow it to be over-ridden on a per-test basis.
It would be ideal to have a unit test that loads a test page but then intentionally doesn't receive the expected events/measurements.
| Assignee | ||
Comment 1•8 years ago
|
||
Basic pageload timeout support for raptor firefox and chrome
Assignee: nobody → rwood
Status: NEW → ASSIGNED
| Assignee | ||
Comment 2•8 years ago
|
||
Comment on attachment 8962868 [details] [review]
https://github.com/rwood-moz/raptor/pull/19
I'll file a separate bug for adding a test for this (as I'm not even sure if end-to-end pytest/unit tests are possible).
Attachment #8962868 -
Flags: review?(ahalberstadt)
Comment 3•8 years ago
|
||
Yes, end-to-end tests are definitely possible, it would involve running the 'raptor' command in a subprocess. It will be a bit of a pain to set up, the tricky bits will be getting 'firefox' and 'chrome' binaries to test. There's some prior art in mozilla-central for this:
https://searchfox.org/mozilla-central/source/testing/mochitest/tests/python/test_basic_mochitest_plain.py#21
In order to find a firefox binary, that uses this fixture (which is conveniently already vendored into this repo):
https://searchfox.org/mozilla-central/source/testing/mozbase/moztest/moztest/selftest/fixtures.py#97
Though it currently only works in mozilla-central.
Comment 4•8 years ago
|
||
Comment on attachment 8962868 [details] [review]
https://github.com/rwood-moz/raptor/pull/19
Thanks, lgtm.
Attachment #8962868 -
Flags: review?(ahalberstadt) → review+
| Assignee | ||
Comment 5•8 years ago
|
||
(In reply to Andrew Halberstadt [:ahal] from comment #3)
> Yes, end-to-end tests are definitely possible, it would involve running the
> 'raptor' command in a subprocess. It will be a bit of a pain to set up, the
> tricky bits will be getting 'firefox' and 'chrome' binaries to test. There's
> some prior art in mozilla-central for this:
> https://searchfox.org/mozilla-central/source/testing/mochitest/tests/python/
> test_basic_mochitest_plain.py#21
>
> In order to find a firefox binary, that uses this fixture (which is
> conveniently already vendored into this repo):
> https://searchfox.org/mozilla-central/source/testing/mozbase/moztest/moztest/
> selftest/fixtures.py#97
>
> Though it currently only works in mozilla-central.
Cool thanks, I filed Bug 1449572 and I'll follow-up on this there.
| Assignee | ||
Comment 6•8 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•