Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
JavaScript Testing and Continuous Integration
Search
Mats Bryntse
March 18, 2015
Technology
1
150
JavaScript Testing and Continuous Integration
jDays 2015
Mats Bryntse
March 18, 2015
Tweet
Share
More Decks by Mats Bryntse
See All by Mats Bryntse
Expect the unexpected - How to deal with JavaScript errors in web applications
mats
1
66
Creating Reusable UI Components with Ext JS
mats
2
790
Dealing with javascript errors in SPAs
mats
0
85
Record.Replay.Reproduce
mats
0
130
Expect the unexpected
mats
0
310
Record.Replay.Reproduce - Dealing with JS errors in modern web apps
mats
0
400
Unit and UI Testing Your Ext JS Web Applications with Siesta
mats
0
200
Siesta Deep Dive
mats
0
310
Testing SalesForce A
mats
0
52
Other Decks in Technology
See All in Technology
少数チームで挑む: SwiftUI, TCA, KMPを用いた 新規動画配信アプリ 「ABEMA Live」の開発について
tomu28
0
520
Algyan イベント振り返り
linyixian
0
180
疲弊しない!AWSセキュリティ統制の考え方 #devio_osakaday1
masahirokawahara
6
5.8k
社内勉強会運営のコツ
senoo
6
1.1k
コードを書く隙間を見つけて生きていく技術/Findy 思考の現在地
fujiwara3
24
4.8k
Postman v10リリース後を振り返る
nagix
0
120
LLM とプロンプトエンジニアリング/チューターをビルドする / LLM and Prompt Engineering and Building Tutors
ks91
PRO
0
220
SIEMを用いて、セキュリティログ分析の可視化と分析を実現し、PDCAサイクルを回してみた
coconala_engineer
0
200
Next'24 事例セッションの紹介とクラウド資格を活用したキャリア形成について語りMuscle
yasumuusan
0
270
[PlatformCon 24] Platform Orchestrators: The Missing Middle of Internal Developer Platforms?
danielbryantuk
0
170
コンテナセキュリティの基本と脅威への対策
kyohmizu
3
670
o11y入門_外形監視を利用したWebアプリケーションへの最適なモニタリング_TechBrew
k5k
2
100
Featured
See All Featured
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
13
1.5k
Web development in the modern age
philhawksworth
201
10k
Optimizing for Happiness
mojombo
369
69k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
6
990
StorybookのUI Testing Handbookを読んだ
zakiyama
10
4.6k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
39
4.4k
GraphQLの誤解/rethinking-graphql
sonatard
49
9.2k
Thoughts on Productivity
jonyablonski
57
3.8k
Visualization
eitanlees
135
14k
Building Your Own Lightsaber
phodgson
97
5.7k
A Philosophy of Restraint
colly
195
16k
Documentation Writing (for coders)
carmenintech
59
3.9k
Transcript
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