public icon indicating copy to clipboard operation
public copied to clipboard

Ember-cli add-on

Open technomage opened this issue 10 years ago • 16 comments

It would be good to directly support the ember-cli environment. It has well defined test structure using QUnit and currently supports PhantomJS. Having wallaby support direct code coverage and IDEA integration on top of this would be worth paying for.

technomage avatar Feb 16 '15 19:02 technomage

+1

simonihmig avatar Mar 06 '15 14:03 simonihmig

+1

Techbrunch avatar Mar 19 '15 12:03 Techbrunch

+1

rotatingJazz avatar May 23 '15 04:05 rotatingJazz

+1

j-carvalho avatar Sep 10 '15 14:09 j-carvalho

+1

olegdovger avatar Jan 09 '16 12:01 olegdovger

+1

ArranMcCabe-zz avatar Jan 28 '16 11:01 ArranMcCabe-zz

+1

waheedel avatar Jan 28 '16 21:01 waheedel

+1

ccoffey avatar Jan 28 '16 21:01 ccoffey

+1

mckenna avatar Jan 29 '16 11:01 mckenna

:+1:

brandonweiss avatar Feb 16 '16 03:02 brandonweiss

@ArtemGovorov Any word on this? It's been more than a year. Even a rough guide would be nice.

brandonweiss avatar May 04 '16 06:05 brandonweiss

@brandonweiss No news on this one. It's also not in any of our close plans. I will post some update here if anything changes.

ArtemGovorov avatar May 04 '16 07:05 ArtemGovorov

I would definitely like this integration - I am having nightmares getting my Ember tests working in Webstorm with the wallaby plugin. What would be involved in integrating it as a supported platform? Just asking in case it something someone could help with.

deedubbleyoo avatar May 04 '16 18:05 deedubbleyoo

@deedubbleyoo I haven't worked with ember-cli and have a pretty much zero experience with it. From what I can briefly see in ember-cli docs (the testing side of things), it is qunit (with some helpers?) + ES2015 (modules and the rest). If ember-cli builds ES6 modules/CommonJs similar to how webpack or browserify do it, then the main (and possibly the only) thing required is a postprocessor (to build ES6 modules into something that a browser environment can execute).

Fortunately, this part of wallaby is easily extensible. For example, webpack and browserify support are implemented as open source postprocessors. Perhaps ember postprocessor can be implemented in the same way.

As an alternative, one may just try to use wallaby supported modules bundlers, like webpack and browserify to create a testing configuration. So it'll be qunit as a testing framework, babel to compile ES2015 and webpack or browserify for imports/CommonJs. While using a different module bundler for the task may seem strange, but it's for testing only and if it works and gets your code tested, then why not. So if anyone checks and finds out if this approach works, let me know.

ArtemGovorov avatar May 05 '16 00:05 ArtemGovorov

@ArtemGovorov I just though about moral side of using different bundler for testing, and I was scared of those differences. But it sounds very reasonable!

yevt0 avatar Nov 10 '17 18:11 yevt0

+1

RyanGuild avatar Apr 18 '19 23:04 RyanGuild