Closed Bug 1108682 Opened 10 years ago Closed 7 years ago

Run mochitest browser chrome tests or similar against the marionette server

Categories

(Remote Protocol :: Marionette, defect)

Product:
Remote Protocol
Component:
Marionette
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: chmanchester, Unassigned)

References

Details

(Keywords: pi-marionette-server)

Attachments

(1 file, 1 obsolete file)

MozReview Request: Bug 1108682 - Run mochitest-browser tests for the marionette server.
39 bytes, text/x-review-board-request
Details
We can do this with mochitest-browser tests. This will be limited to certain things, and will probably only make sense once bug 1107706 lands (if ever).
/r/1305 - Bug 1108682 - Run mochitest-browser tests for the marionette server. Pull down this commit: hg pull review -r d3b92a78810e6ac026952cf00a7c9b0cf40a98a7
what benefit would this have over doing it the way we are currently doing things?
Flags: needinfo?(cmanchester)
Keywords: ateam-marionette-server
It was mentioned in passing that one of the benefits of :ato's refactor in bug 1107706 would be a more testable design. I realized that while we extensively test the server via the client, there are no unit tests (I don't think) that test the behavior of individual functions in the server.
Flags: needinfo?(cmanchester)
ok cool, let's see about getting this in then. most of the time I prefer full stack testing but can see value in this too
Summary: Run tests against the marionette server → Run mochitest browser chrome tests or similar against the marionette server
Attachment #8533259 - Attachment is obsolete: true
Closing this as have done a lot in the ways of testing since this raised.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: