Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
JavaScript Testing and Continuous Integration
Search
Mats Bryntse
March 18, 2015
Technology
230
1
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
JavaScript Testing and Continuous Integration
jDays 2015
Mats Bryntse
March 18, 2015
Transcript
56 slides
Mats Bryntse, Bryntum JS Testing and Continuous Integration @Bryntum
Intro | PRESENTATION Who am I?
Agenda | Content Unit tests UI tests Continuous Integration •
Writing a unit test • Using PhantomJS • Hello world sample • Testing a view • Recording a UI test • Application test • TeamCity • Code Coverage • Statistics • Cloud Testing
Intro | DESCRIPTION Less Theory, More Real World
Intro | WHY Hands up: Who is testing their JS?
Intro | WHY
Intro | WHY 1. Productivity & confidence in code 2.
Frameworks contain bugs 3. So does your code (and mine) 4. Refactoring & code handover 5. Fix bugs once
Intro | TERMINOLOGY Terminology: what does testing mean for a
JS developer?
Intro | TERMINOLOGY Unit tests, UI tests, Application tests..?
Intro | Test pyramid JS Unit tests App Tests UI
tests
Intro | Common company scenario Backend unit tests App Tests
Unit Tests Introduction
Intro | Unit Tests • should focus on a single
JS class (“unit”) • should not involve DOM • is pure logic, runs very fast • is perfect for pre-commit hooks A unit test…
Intro | Unit Tests describe('A simple Model test', function (t)
{ t.it('Should do something', function(t) { var user = new User({ name : ‘Bob’ }); t.expect(user.name).toBe(‘Bob’); }); });
Intro | Unit Tests describe('A simple Model test', function (t)
{ t.it(‘Will not run', function(t) { … }); t.iit(‘Isolate this section', function(t) { … }); });
Unit tests | Intro •Should be your #1 priority •Cover
your most important JS classes, code that is reused •Run often, before commit, daily, nightly. •Use TDD approach + BDD style for readability
Unit tests | TDD basics 1. Make the unit test
fail 2. Implement 3. Make the test pass 4. Refactor, Repeat
Unit tests | Writing a unit test Unit testing demo
Testing your UI Functional testing
UI tests | Intro Manually writing UI tests takes time
UI tests | Intro UI tests are more fragile &
run slower than unit tests
UI tests | Intro Understanding CSS and ComponentQuery is key
UI tests | Intro •UI “unit test” of a single
UI component •Or Application test, open index.html and test it Two main types of UI tests
UI tests | Intro UI Unit test demo
Application Tests Introduction
Application tests | Intro •Black box testing, go to index.html…
•Runs all the code of your application •Does app work or not?
Application tests | Challenges •Database needs to be put in
a known state pre test start •Slow •Fragile, race conditions •Errors likely harder to find
Application tests | Intro Using an Event Recorder
Application tests | Event recorder •Great for application tests •Records
user actions: clicks, types, drag drop •Can be used by a non-programmer •Big timesaver
Application tests | Event recorder Let’s try the recorder
Application tests | Monkey tests Monkey testing
Application tests | Monkey tests •Random UI testing •Clicks, drags
etc. in your UI •Finds unhandled exceptions •Free testing help. 0€
Application tests | Monkey tests Cost breakdown: 5€ * 0
= 0 5€
Application tests | Monkey tests Monkey testing demo
Application tests | Monkey tests Cheap/Free way to catch bugs
Finding bugs | Error logging Error Logging
Finding bugs | Error logging Unhandled JS exception: What does
the user see?
Finding bugs | Error logging Nothing
Finding bugs | Error logging win.onerror = function (message, file,
line, column, errorObj) { // Log it };
Finding bugs | Error logging Demo - it’s simple
Finding bugs | Git hooks Pre-commit hook
Finding bugs | Pre-commit hook •Pre-commit hooks are great to
keep code base clean •Check JsHint •Run unit tests
Finding bugs | Pre-commit hook A sample Git pre-commit hook
Continuous Integration TeamCity, Code Coverage & Statistics
Continuous Integration | Intro •Automated builds •Nightly test suite execution
•Finding errors early => Code quality => Motivated developers •Enables Continuous Delivery Purpose of having CI:
Continuous Integration | Intro Always ready to release!
Continuous Integration | Intro •Bryntum uses TeamCity •Test suites run
every 2 hours in Chrome •Full test suites executed nightly •Reports, statistics, charts and code coverage
Continuous Integration | TeamCity Let’s checkout TeamCity
Continuous Integration | Cloud testing So…running in multiple browsers?
Continuous Integration | Cloud testing •Need to create Virtual Machines
for each version of IE •Total: Chrome, Safari, FF, IE 7-11 => 8 VMs •Managing such a farm can be very time consuming
Continuous Integration | Cloud testing •Siesta integrates with both BrowserStack
and Sauce Labs •Run tests easily in any OS and Browser combination •No need to setup your own VM farm •Read more on the Bryntum blog…
Continuous Integration | Cloud testing Launching tests in BrowserStack
Rounding up | Summary •Prioritise JS unit tests •UI tests
•Application & monkey tests •Tips for finding errors early •Continuous Integration
Rounding up | Links •bryntum.com/products/siesta •bryntum.com/blog •teamcity.bryntum.com/guest •browserstack.com/ •saucelabs.com/
Rounding up | Fika Dear Ladies and Gentlemen,
you are now welcome to ”Vinterträdgården” for a lovely coffee break that is sponsored by
Rounding up | Questions Questions? Twitter: @Bryntum
More Decks by Mats Bryntse
See All by Mats Bryntse
Expect the unexpected - How to deal with JavaScript errors in web applications
mats
1
150
Creating Reusable UI Components with Ext JS
mats
2
1.1k
Dealing with javascript errors in SPAs
mats
0
220
Record.Replay.Reproduce
mats
0
200
Expect the unexpected
mats
0
540
Record.Replay.Reproduce - Dealing with JS errors in modern web apps
mats
0
600
Unit and UI Testing Your Ext JS Web Applications with Siesta
mats
0
270
Siesta Deep Dive
mats
0
400
Testing SalesForce A
mats
0
140
Other Decks in Technology
See All in Technology
人の努力に頼らないセキュリティをエンジニアリングする在り方 / An approach to engineering security that does not rely on human effort
carta_engineering
0
220
SREのためのFinOps入門
muziyoshiz
3
1.6k
人間+AIを「チーム」としてプロセスを再設計する
littlehands
4
3.5k
攻撃と守りは何が変わり、何が変わらないのか~最近の不正アクセスから考える、リスク評価と標準の使いどころ
oidfj
2
210
業務の傍らで進める改善ループエンジニアリング
bengo4com
1
200
自動計装なしでECSサービスをApplication Signalsに載せるまで
ota1022
2
420
E2E Test というハーネス — AI時代の自動テスト民主化
daishukojima
10
5.8k
MCPでネットワーク障害調査を自動化する前に直すべき3つのこと
yama3133
1
630
統制されたID・権限をどう利用するか : DPoP/FAPIによるAPIセキュリティ強化
oidfj
1
190
変更差分を読むために環境を整備しよう
pipepasta
1
470
AI時代における医療情報システムのセキュリティ / Security of Healthcare IT Systems in the AI Era
henryofficial
0
190
IP重複は"ランディングVPC"で受け止める ― PrivateLink と Transit Gatewayによるマルチテナント接続基盤の設計
hatahata021
3
250
Featured
See All Featured
Code Review Best Practice
trishagee
74
20k
Efficient Content Optimization with Google Search Console & Apps Script
katarinadahlin
PRO
1
1k
Fireside Chat
paigeccino
43
4.1k
Why You Should Never Use an ORM
jnunemaker
PRO
61
10k
[RailsConf 2023] Rails as a piece of cake
palkan
59
7.2k
Art, The Web, and Tiny UX
lynnandtonic
304
22k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
333
23k
Jamie Indigo - Trashchat’s Guide to Black Boxes: Technical SEO Tactics for LLMs
techseoconnect
PRO
0
760
エンジニアに許された特別な時間の終わり
watany
109
250k
Reflections from 52 weeks, 52 projects
jeffersonlam
356
22k
YesSQL, Process and Tooling at Scale
rocio
174
15k
Taking LLMs out of the black box: A practical guide to human-in-the-loop distillation
inesmontani
PRO
3
2.5k