Erik Vold Reporter
	Description • 9 years ago

There should be a easy way to unit test add-ons, for example with travis-ci, as it was with `jpm` and `jpm-mobile` for Jetpacks (although it now appears broken...).

Without this testing add-ons to make sure that they work is a manual process, and much much more cumbersome than developing an add-on with `jpm` was.

	Erik Vold Reporter
	Comment 1 • 9 years ago

This is pretty important for any existing Fx extensions that wants to port to the Webextension api.  Since this is a thing that Mozilla claims to want to support (ie porting) then this should be P1 right?

	Andy McKay
	Comment 2 • 9 years ago

Its something we should do, a P1 without context doesn't make much sense though.

	Erik Vold Reporter
	Comment 3 • 9 years ago

(In reply to Andy McKay [:andym] from comment #2)
> Its something we should do, a P1 without context doesn't make much sense
> though.

I mentioned the context in comment 0...  what is missing iyo?

Building a webextension is a waste of time for anyone that cares about TDD at the moment, and I thought testing is something that Mozilla cares about..

	Andy McKay
	Comment 4 • 9 years ago

I'm not sure why you are needinfo'ing me, what can I help with?

	Erik Vold Reporter
	Comment 5 • 9 years ago

(In reply to Andy McKay [:andym] from comment #4)
> I'm not sure why you are needinfo'ing me, what can I help with?

see comment 3

	Andy McKay
	Comment 6 • 9 years ago

Being tracked in web-ext https://github.com/mozilla/web-ext/issues/5, unless anyone wants to do anything different in here.

	Kumar McMillan [:kumar] Assignee
	Comment 7 • 8 years ago

Closing since this is tracked in git (as mentioned) https://github.com/mozilla/web-ext/issues/5