Google Chrome Developers765 тыс
Следующее
Опубликовано 16 декабря 2015, 21:58
Elements that need to get data from a backend service can be tricky to test. Do you need to startup your own test server just to verify an element does what it's supposed to? Is that even a good idea? Today on Polycasts I'll show you have to use Web Component Tester and a library called Sinon.js to mock your back end and speed up your unit tests. By mocking your backend you can verify that your element's work in isolation, which is a crucial step to having good overall test coverage of your app.
Web Component Tester
github.com/Polymer/web-compone...
Iron Ajax
github.com/PolymerElements/iro...
Sinon.js
sinonjs.org
Chai Expect
chaijs.com/api/bdd
Polymer Slack: bit.ly/polymerslack
Subscribe to the Chrome Developers channel at goo.gl/LLLNvf
Web Component Tester
github.com/Polymer/web-compone...
Iron Ajax
github.com/PolymerElements/iro...
Sinon.js
sinonjs.org
Chai Expect
chaijs.com/api/bdd
Polymer Slack: bit.ly/polymerslack
Subscribe to the Chrome Developers channel at goo.gl/LLLNvf
Свежие видео
Случайные видео