aboutsummaryrefslogtreecommitdiffstats
path: root/docs/src/templates/docs-scenario.html
AgeCommit message (Collapse)Author
2014-02-16chore(doc-gen): new docsPeter Bacon Darwin
chore(doc-gen): implement dgeni
2013-05-21chore(package.json): kill version.yaml in favor of package.jsonIgor Minar
all versioning info is now in package.json and that's where the build scripts read it from
2012-11-11chore(docs): fix docs-scenario.htmlIgor Minar
2012-08-24chore(docs): use GAE and Google CDN for docsIgor Minar
Short summary: if you use local node server everything should work as before, if you use GAE, everything should work now as well, but we pull assets from CDN. - GAE doesn't support ':' in filenames, so I had to replace it with '_' but only in the filename, all servers were reconfigured to rewrite the urls from : to _ when doing file lookup - We now pull angular assets from google CDN when deployed on GAE (locally or in production). When running on a non GAE server we pull assets from ../ directory as before - Since only certain versions of Angular are available on CDN and we want to be able to autodeploy docs, I had to pin down the Angular files to a "stable" version when running on GAE
2012-04-12style(docs-scenario.html): rename <angular/> to AngularJS in the titleIgor Minar
2011-05-19JSTD adapter for running e2e testsVojta Jina
Couple of changes into angular.scenario runner: - add autotest config (runs tests when document ready) - update ObjectModel (forwards events) - use only one ObjectModel instance for all outputters - expose error msg and line number in ObjectModel.Spec and ObjectModel.Step - fix generating spec.ids - fix 'html' output so that it does not mutate ObjectModel Couple of changes into docs / generator: - rename copy -> copyTpl - move docs/static into docs/examples (to avoid conflict with jstd proxy) Running all docs e2e tests: ======================================================== 1/ compile angular-scenario, jstd-scenario-adapter >> rake compile 2/ build docs >> rake docs 3/ start jstd server >> ./server-scenario.sh 4/ capture some browser 5/ run node server to serve static content >> node ../lib/nodeserver/server.js 6/ run tests >> ./test-scenario.sh
2011-01-24fixed example rendering, add tests for it.Misko Hevery
2011-01-10complete rewrite of documentation generationMisko Hevery
- romeved mustache.js - unified templates - improved testability of the code