Add webdriver unit tests for indefinite script timeout
Categories
(Testing :: geckodriver, enhancement)
Tracking
(firefox67 fixed)
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | fixed |
People
(Reporter: r2hkri, Assigned: r2hkri)
References
Details
Attachments
(1 external file)
Follow-up to 1128997
> The only thing I actually miss in this patch are some more unit tests for the
> webdriver crate. I don't want to run wdspec to verify if changes in
> webdriver/geckodriver work. Running the Rust unittest is way less expensive.
> Would you mind getting those tests added in a follow-up bug?
> Just create one and upload the new patch. I would appreciate and be happy to
> review it.
Add unit tests to cover webdriver functionality that was suggested and implemented in linked bug (difference between undefined and null when serializing and de-serializing script timeout values).
Comment 1•7 years ago
|
||
Can you be more specific in the description what test you are going
to add here? Otherwise I fear we risk scope creep.
Comment 2•7 years ago
|
||
Thank you for filing this bug. Do you also want to work on it, and add the remaining tests?
(In reply to Andreas Tolfsen ⦗:ato⦘ from comment #1)
Can you be more specific in the description what test you are going
to add here? Otherwise I fear we risk scope creep.
Test cases that check serializing/deserializing null properly like:
fn test_json_timeouts_response_with_null_timeout() {
let json = r#"{"value":{"script":null,"pageLoad":2,"implicit":3}}"#;
let data = WebDriverResponse::Timeouts(TimeoutsResponse::new(None, 2, 3));
check_serialize(&json, &data);
}
(In reply to Henrik Skupin (:whimboo) [⌚️UTC+1] from comment #2)
Thank you for filing this bug. Do you also want to work on it, and add the remaining tests?
Yes, I can work on it.
Add tests that check serialization and deserialization for indefinite script timeout
Updated•7 years ago
|
Comment 6•7 years ago
|
||
| bugherder | ||
Description
•