Open
Bug 1507281
Opened 6 years ago
Updated 2 years ago
Flex devtools API tests should be refactored to have separation of concerns
Categories
(DevTools :: General, enhancement, P3)
DevTools
General
Tracking
(Not tracked)
NEW
People
(Reporter: bradwerth, Unassigned)
References
Details
When we created the Flex devtools API, we started with a monolithic test structure: one test that exercised the whole API shallowly. As we've added more properties to the objects returned by the API, that monolithic test is increasingly hard to maintain and its shallowness is becoming a liability. To fix this, we should create multiple tests that each thoroughly exercise values returned by the API. They could be organized around these concerns:
* item position and size
* item clamping
* item growth/shrinking
* line position and size
* line baselines
* container axis directions
Reporter | ||
Comment 1•6 years ago
|
||
We probably should also move these tests from dom/flex/test/chrome to devtools/client/inspector/flexbox/test, where similar tests already reside.
Reporter | ||
Updated•4 years ago
|
Assignee: bwerth → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•