testing this lib

[btford]

We have unit tests for each individual plugin, but some high-level integration tests for angular-hint itself would be nice.

I think we should flesh out the example app, then use Protractor to E2E test this, asserting that things are logged correctly.

[ealtenho]

@btford I'm trying to set up initial tests 14bb413 but I'm having trouble wiring things together I believe because of the order in which bootstrapping occurs? Any advice? Should I be focusing on E2E tests instead?

[btford]

We talked in-person, but for posterity: individual modules should have unit tests, this repo should have mostly (maybe entirely) E2E tests.

[btford]

This is resolved now, right?

[btford]

@ealtenho can we run some very simple E2E tests with protractor?

[ealtenho]

Yes @btford in the commit e1e7cdb I just pushed I added basic protractor tests . I think these tests will be much less irregular when angularHintLog creates similarly formatted output for all modules (currently some use console.log, some console.group, some console.groupCollapsed).

I am also having a strange issue with my ng-hint default test (commented out in this commit). When I run protractor it does not seem to resolve the route for /allHint.

What is the next step to get continuous tests running?

[ealtenho]

Update: e2e tests in /e2e cover all variations of loading modules with ng-hint-include, ng-hint-exclude, ng-hint or no hinting at all.

We also plan to have a sample application that demonstrates the behavior of AngularHint in an application context.

[ealtenho]

There are now passing e2e tests that test the default logging of AngularHint to the console from each of the AngularHint modules. Additionally, the sample applications example and correctExample showcase the function of AngularHint in a realistic setting. This uncovered the bugs described in #36.