Verify tests for path/manifest when manifest updated

NEW
Unassigned

Status

Testing
General
P3
normal
10 months ago
2 months ago

People

(Reporter: gbrown, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 months ago
This is a vague enhancement idea...something to consider.

Currently test-verify is triggered when a test file is modified. It could also be triggered when a .ini file is updated, with verification in this case applied to the entire manifest.

This would be useful when a skip is removed or a skip-if is modified, or tests are otherwise added or removed from a manifest *without* modifying the test. (The normal case is probably that a test file is modified *and* the manifest is updated, which today results in only the modified test coming under scrutiny; that is probably the optimal behavior for that case, and I wouldn't want to see that change.)
(Reporter)

Comment 1

9 months ago
Additionally, if this works, we could then *not* run any task but test-verify when a manifest is updated (bug 1383880 / check with Dustin for implementation details).
(Reporter)

Updated

5 months ago
Priority: -- → P3
(Reporter)

Updated

2 months ago
Assignee: gbrown → nobody
You need to log in before you can comment on or make changes to this bug.