-
Task
-
Resolution: Fixed
-
Major
-
None
-
None
-
(likely) Karma / Protractor in AngularJS
-
NDS Sprint 14, NDS Sprint 16
As described in ndslabs issue #23, unit / integration are something that NDS Labs currently lacks. This can cause new and old issues alike to bubble up unnoticed until a manual round of testing reveals them. While I am not familiar enough with Go to recommend technologies, there seem to be some existing methodologies for testing Go applications.
There are several options regarding unit or integration/e2e testing in AngularJS applications. Many such options are enumerated here: http://stackoverflow.com/questions/300855/javascript-unit-test-tools-for-tdd
Two of the more common choices in this area are either Jasmine or Mocha + Chai + Sinon for writing test specs (Ruby style), with Karma + Protractor for running tests specs.
- is related to
-
NDS-173 Investigate Build/Release tasks for production JavaScript
-
- Resolved
-
-
NDS-1150 Set up staging Workbench instance for CI to use for testing
-
- Closed
-
-
NDS-1151 TravisCI YAML file for ndslabs repo
-
- Closed
-
-
NDS-579 Prototype performance load test process
-
- Resolved
-
-
NDS-725 Run protractor from within angular-ui container
-
- Resolved
-
-
NDS-230 Investigate code / doc generation techniques
-
- Closed
-
- relates to
-
NDS-704 Dockerize integration tests
-
- Resolved
-
- links to
- Wiki Page
-
Wiki Page Loading...