chore(scenarioRunner): do not publish updates to bower/npm

[btford]

Suggested by @IgorMinar.

Since this has been in "maintenance mode" for a while, it's probably good to start winding down on it and encouraging users to switch to protractor.

[wpannell]

@IgorMinar Can we still use browserTrigger.js for unit testing directives? I've gotten a lot of value from it for test-driving directives from the outside-in.

[btford]

@wpannell – I don't see why not

[Narretz]

When this is done, we can also probably close all issues labeled scenario runner

edit: all those that don't concern browserTrigger, that is

[wpannell]

@IgorMinar @btford can you comment on the following: my team provided this issue to caution against using browserTrigger.js for directive testing. Not sure I understand the fear of testing our directives the way the AngularJS core team does. Personally, I've always followed those practices closely without incident.

[petebacondarwin]

@wpannell - while browserTrigger is still only available to external developers via ngScenario, it is perfectly usable.

The point of the comment is that we are not currently providing it in ngMocks as a public function and so you cannot rely on the AngularJS team modifying it to support your own external requirements.

When we finally remove ngScenario we should probably move browserTrigger to ngMocks and then we will have a discussion about what level of support it should get.