I need your help!

[btford]

Following the v0.5.0 release, I wanted to thank everyone that posted reproductions and stack traces, and sent me PRs to fix the issues with the new implementation. I wouldn't have been able to follow-up with fixes if not for your help.

It's clear to me that I haven't given the time to Batarang that it deserves. Several people have forked, or created other extensions to try and fill these gaps. I'd like to invite anyone interested to work with me on making Batarang better.

My priority with Batarang right now is to first improve the testing infrastructure, and then reduce some of the complexity of it's implementation (especially WRT angular-hint). I want to make sure nothing like the issues we say in v0.5.0 happens again, and also make it easier for others to contribute and reason about the code.

After that, I'm happy to provide guidance as far as new features and improvement, but I'm hoping to get others involved so this project continues to have good momentum even when my focus is on other things (like github.com/angular/router ).

If you're interested in helping, please comment and let me know how you'd like to see Batarang improved. Thanks!

[jkirkpatrick]

I can contribute CI and tests, the project needs them badly. If you document/adopt some Q/A methodology (e.g. Jenkins and git pull requests), release strategy (e.g. All tests must pass and sign off by admin), and stub out some code for testing or make suggestions where to start - I'd be happy to help.

I don't know what specific testing tools/frameworks would be most appropriate here, that's why I'd defer until something was committed or suggested/agreed by community. In my experience, each testing framework has their nuances and I definitely don't know which work well for Chrome Apps - that would be new to me.

I'd also like to suggest finding/using/creating a non-trivial angular application (or 3) to test against.

[krismeister]

@jkirkpatrick travis-ci[https://travis-ci.org] is a good system for opens ource ci and testing. backbone-marionnette[https://github.com/marionettejs/backbone.marionette] is an example of a project which uses travis (see the badges below their logo). Marionette uses mocha[http://mochajs.org/] to run their tests, see their travis.yml file for the node commands.

I think the steps are:

• branch batrang
• setup package.json with mocha and npm install
• get one test to run: expect(true).toBe(true)
• Add the travis.yml file and register with travis
• troubleshoot till it passes tests in travis

I don't have bandwidth this month to help out but @btford everyone uses this project because its the most popular(& only that i know of) solution out there to debug angular. No biggie about the last release it happens, keep it up.

update - sorry i see now you wanted to use protractor and selerium - in your other post. It sounds like differences in chrome versions was the cause of v0.5.0. No thats more complicated than I've dealt with before. I was saying mocha, because its easy to setup and write tests for. But its clearly not different real browser running.

[jkirkpatrick]

update -- gulp, protractor, selenium in the works

[gkalpak]

I was under the impression that most angular projects used jasmine. If that's the case, wouldn't it be better to keep things uniform ?

[jkirkpatrick]

If I understand @btford's immediate problem, which I did not at first - a way to instrument and compare testing multiple versions of the chrome extension on one machine - not exactly the same thing as unit testing the code itself (which it also requires). Side-By-Side installs and testing are always a bit tricky. Another way might be to use a script runner and a series of shell scripts to manually installs/uninstall the plugin... but that's ugly compared to #193

Using the chrome webdriver to load profiles IS different that what most angularjs projects require; the nature of the project is a chrome-extension/debugger/tool, not an angularjs application, although the opposite argument might be made for hint.js. Protractor isn't as popular as jasmine (I hadn't heard of it before last night), but it's still a very popular tool for testing angularjs apps.

Protractor can load a url or locally packaged file for tests - Jasmine/mocha/chai/vows could provide additional coverage in that case.

[btford]

To clarify, my intention is to be able to run Chrome in Protractor with the extension disabled as a sort of integration test. I'd prefer to move discussion about how to accomplish this to #193 (we're on the right track, but there are caveats). Thanks for your help, all.

[levithomason]

I've been using Batarang for just about 2 years now. I've run into some issues with the latest build. I'd love to help.

I'm experienced enough with gulp, protractor, and selenium. I've got (some) experience angular powered chrome extensions. Where is the most helpful place to plug in?

[scheffield]

I'd like to help as well. Where can/should I start?

[SomeKittens]

Anyone who wants to help can start by tackling an issue in the https://github.com/angular/angular-hint project (the engine behind Batarang).