Open Bug 1586253 Opened 5 years ago Updated 10 months ago

test_json_timeout_parameters_with_invalid_values should test invalid timeout object values separately

Categories

(Remote Protocol :: Marionette, task, P3)

task

Tracking

(Not tracked)

People

(Reporter: ato, Unassigned, Mentored)

Details

(Whiteboard: [lang=rust])

test_json_timeout_parameters_with_invalid_values tests the bounds of the timeouts configuration object in a single, big JSON Object. This means any of the checks has the potential of failing the whole test case. This in turn means we are lacking test coverage for the two timeouts that we don’t test.

The solution is to split the test in three, where each timeout type is tested separately.

The priority flag is not set for this bug.
:whimboo, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(hskupin)
Type: defect → task
Flags: needinfo?(hskupin)
Priority: -- → P3
Whiteboard: [lang=rust]
Severity: normal → S3
Severity: normal → S3
Component: geckodriver → Marionette
Product: Testing → Remote Protocol
Version: Version 3 → unspecified
Mentor: hskupin
You need to log in before you can comment on or make changes to this bug.