Closed Bug 978952 Opened 10 years ago Closed 10 years ago

standup trival mocha / chai test page

Categories

(Hello (Loop) :: Client, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
mozilla33

People

(Reporter: dmosedale, Assigned: dmosedale)

References

Details

Attachments

(1 file)

In order to unblock folks writing unit tests with the JS code on Loop front-end stuff, Niko and I paired this morning on a dummy test with Mocha and Chai.

The PR imports Mocha 1.17.1, and Chai 1.9.0.  They are unit-testing frameworks only, and won't be shipped as part of a product.  Both use MIT licenses:

https://github.com/visionmedia/mocha/blob/1.17.1/LICENSE
https://github.com/chaijs/chai/tree/1.9.0#license

so I'd be quite stunned if there were a problem from that point of view, and suggest we land on the master branch of Adam's fork of gecko-dev, and back it out if there's a problem.
Gerv, is there any special process we need to do when importing code like this?  The intent is that we want to hope to land this stuff on the master mozilla-central repo down the line a bit, and we're using this branch to flag potential issues before we do.
Flags: needinfo?(gerv)
Not shipping + MIT-license == no problem.

Gerv
Flags: needinfo?(gerv)
Pull request merged; not yet closing, as I've seen abr use [leave-open] on the other bugs, and I'm not sure what his logic is there.
(In reply to Dan Mosedale (:dmose) from comment #4)
> Pull request merged; not yet closing, as I've seen abr use [leave-open] on
> the other bugs, and I'm not sure what his logic is there.

Sorry; I try to indicate the reason for adding [leave-open] when I add it, although I may have missed it somewhere.

In any case, I think this can be closed now that it's landed.

For t-crossing and i-dotting purposes: in the future, please do a formal r?/r+ with someone before merging PRs into the tree we're using, even if they're just third-party files. If we plan to do a bulk landing of our tree on m-i in the future, I believe that we need to be able to truthfully claim that every file went through the same review process as it would have to land on the tree directly.
Comment on attachment 8384844 [details] [review]
Link to Github pull-request: https://github.com/adamroach/gecko-dev/pull/4

Dan had got confused last night about the my review intentions. I've just reviewed the additional changes and they are fine. So post-landing r=Standard8.
Attachment #8384844 - Flags: review?(standard8) → review+
Yeah, this was a mistake on my part; will catch in the future.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla33
I don't think this needs QA before release. Please needinfo me to request specific testing.
Whiteboard: [qa-]
Flags: qe-verify-
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: