Rob Wormald recognized that we had no plunker for a simple component test. Inspired improved learning path for testing including:
* Add plunkers for both inline and external template versions of the simplest `BannerComponent`
* Added the banner-specs for that purpose and also a quickstart-specs in the setup folder
* Adjusted prose in testing and setup-systemjs-anatomy to call these out
* Moved testing of external template spec earlier in the guide because it is likely to be needed right away.
* Add comments on the optional "testing" folder and corrects var names to match
* Leaves Jasmine Spec Runner output visible when tests finish
For specific plunkers, e.g. "QuickStart (reboot edition)" PR #2762, that shouldn't have AppModule or main.ts
Rescinds the automatic bootstrapping and exclusion of `main.ts` in #2786 and #2756
Only autoBootstraps when `window.autoBootstrap === true`.
* plunker builder removes files and scripts not needed in plunkers (e.g., systemjs.config.js)
* no longer adds placeholder README.md (deemed a distraction)
* tag is now "Angular" instead of "Angular2"
* new plnkr.json "includeSystemConfig" option adds systemjs.config.js back; needed for testing plnkrs.
* incidentally changes comment "Polyfill(s)" to "Polyfills" in all index.html
Bug in Jasmine v.2.5.x. Stick with v.2.4.1 (as karma-jasmine does) until the following issue is resolved:
https://github.com/jasmine/jasmine/issues/1231
Unfortunately, there is no `@types/jasmine` for v.2.4 but only for v.2.5.
* chore(test): add protractor4
* fix lint, remove boilerplate files, fix less gen
* separate scripts between package.json
* ignore a2docs.css in boilerplate
* remove tslint in _examples
Fix#1684
While looking at this, I saw that plunkers were getting some unintended unit testing files and added them to the default plunker builder ignore.
Filipe Silva
Ward Bell
Jesús Rodríguez
Rob Wormald
Peter Bacon Darwin
Tero Parviainen