angular.js/test/e2e, branch g3_v1_2 chore(doc-gen): add formatted error messages to error pages 2014-02-20T14:41:32+00:00 Peter Bacon Darwin 2014-02-20T10:57:40+00:00 d7a73e41eddf3b8f06b87535c5ba6cc3196cbffd This got missed in the doc migration: When there is an error in an Angular app, extra information is placed in the URL, which can be used by the docs application to display a more useful message. This fix adds that back in. The error message templates are extracted by the minerr tool during build and put into the errors.json file. The errors-doc processor will load this up and attach these message templates to the error docs. The display of these templates was already in place, via the errorDisplay directive in docs/app/js/errors.js. (Also, moved the error.template.html file into the angular.js repository from the dgeni-packages repository as this is specific to the angular.js project and all the other error related stuff is in here. Finally, also, added an e2e test that checks that minerr formatted messages are displayed correctly. Closes #6363 
This got missed in the doc migration: When there is an error in an
Angular app, extra information is placed in the URL, which can be used
by the docs application to display a more useful message.

This fix adds that back in.  The error message templates are extracted
by the minerr tool during build and put into the errors.json file. The
errors-doc processor will load this up and attach these message templates
to the error docs.

The display of these templates was already in place, via the errorDisplay
directive in docs/app/js/errors.js.

(Also, moved the error.template.html file into the angular.js repository
from the dgeni-packages repository as this is specific to the angular.js
project and all the other error related stuff is in here.

Finally, also, added an e2e test that checks that minerr formatted
messages are displayed correctly.

Closes #6363
test(docs): add check for resilience to trailing slashes, etc. 2014-02-18T06:36:34+00:00 Peter Bacon Darwin 2014-02-18T06:35:44+00:00 4f937bda18bd577febcb29e3969fe72b400d1a61 






test(docs-app-e2e): refactor test inline with new docs app
2014-02-16T19:03:43+00:00

Peter Bacon Darwin

2014-02-14T11:44:41+00:00

9878fee2992a845dff1e3e083f487013ebde8064

The links to code elements have now changed: api/ng.directive:ngClick ->
api/ng/directive/ngClick.

Examples now run inside iframes, so we need to instruct Protractor to
switch to the example iframe.





The links to code elements have now changed: api/ng.directive:ngClick ->
api/ng/directive/ngClick.

Examples now run inside iframes, so we need to instruct Protractor to
switch to the example iframe.







chore(testing): run end to end tests on firefox and safari as well as chrome
2014-02-05T23:39:59+00:00

Julie

2014-01-31T02:49:58+00:00

0e85ca9ddb5f259908400463764fd6141977b341

Update the Travis and Jenkins configs to run protractor tests on Safari and Firefox as well,
and make the Travis tests run output XML and turn off color.

Fix tests which were failing in Firefox due to clear() not working as expected.

Fix tests which were failing in Safari due to SafariDriver not understanding the minus key,
and disable tests which SafariDriver has no support for.





Update the Travis and Jenkins configs to run protractor tests on Safari and Firefox as well,
and make the Travis tests run output XML and turn off color.

Fix tests which were failing in Firefox due to clear() not working as expected.

Fix tests which were failing in Safari due to SafariDriver not understanding the minus key,
and disable tests which SafariDriver has no support for.







test(docs): add protractor tests for docs app
2014-01-10T06:41:52+00:00

Jeff Cross

2014-01-09T19:21:54+00:00

039b990d8dc73e59418114b49c36797e44127c76

Closes #5437





Closes #5437