Implement mocking provider to test UI (and API)

VERIFIED FIXED in mozilla2.0b1

Status

()

defect
P2
normal
VERIFIED FIXED
9 years ago
9 years ago

People

(Reporter: Unfocused, Assigned: mossop)

Tracking

Trunk
mozilla2.0b1
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite +
in-litmus -

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [rewrite])

Attachments

(1 attachment)

The new API backend allows us to add custom providers. We should have a mocking provider that can be controlled by unit tests, so we can test the UI (and potentially the API) without jumping through hoops, and needing restarts, etc.
Flags: in-testsuite?
Flags: in-litmus-
Priority: P1 → P2
Posted file WiP v1
Work so far. My plan was to allow providers to be created and registered as needed (requires bug 566760 to be fixed).
Dave: See attached file.
Assignee

Updated

9 years ago
Assignee: nobody → dtownsend
Perfect is the enemy of the good here. I don't think it is worth trying to make a mock provider that can do everything perfectly in one shot. Instead I've added the bulk of this code into the test suite in bug 562795 and started using it for testing. It doesn't support installs and doesn't really do any events yet, but it is a useful start and the other bits can grow as and when we need them.
Assignee

Updated

9 years ago
Status: NEW → ASSIGNED
Just going to call this fixed on the basis that we have one now. It needs more work but that can just happen organically as new tests need it, this bug won't be much use anymore.

Fixed mostly by the code in bug 562795.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Flags: in-testsuite? → in-testsuite+
Resolution: --- → FIXED
Marking as verified fixed based on its landing and the first passing tests.
Status: RESOLVED → VERIFIED
Target Milestone: --- → mozilla1.9.3b1
Version: unspecified → Trunk
You need to log in before you can comment on or make changes to this bug.