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
Testing SalesForce A
Search
Mats Bryntse
January 15, 2015
0
63
Testing SalesForce A
Mats Bryntse
January 15, 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
69
Creating Reusable UI Components with Ext JS
mats
2
920
Dealing with javascript errors in SPAs
mats
0
110
Record.Replay.Reproduce
mats
0
150
Expect the unexpected
mats
0
370
Record.Replay.Reproduce - Dealing with JS errors in modern web apps
mats
0
440
Unit and UI Testing Your Ext JS Web Applications with Siesta
mats
0
210
Siesta Deep Dive
mats
0
330
JavaScript Testing and Continuous Integration
mats
1
160
Featured
See All Featured
Testing 201, or: Great Expectations
jmmastey
40
7.1k
It's Worth the Effort
3n
183
28k
No one is an island. Learnings from fostering a developers community.
thoeni
19
3k
Build your cross-platform service in a week with App Engine
jlugia
229
18k
Embracing the Ebb and Flow
colly
84
4.5k
Scaling GitHub
holman
458
140k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
2
170
RailsConf 2023
tenderlove
29
940
How to Ace a Technical Interview
jacobian
276
23k
Automating Front-end Workflow
addyosmani
1366
200k
KATA
mclloyd
29
14k
Optimising Largest Contentful Paint
csswizardry
33
3k
Transcript
Mats Bryntse, Bryntum Testing Web Apps with Siesta @Bryntum
Intro | DESCRIPTION Who am I? Ext JS since 2007
Bryntum: Gantt charts, JS Testing tools
Intro | DESCRIPTION We created Siesta since developing JS components
is very hard.
Webinar | Content Unit tests UI tests Continuous Integration •
Writing a unit test • Using PhantomJS • Hello world sample • Event recorder intro • Testing an Ext JS cmp • Recording a UI test • TeamCity • Code Coverage • Statistics • Cloud Testing + How Siesta can help you test SalesForce apps
Intro | WHY Hands up: Who is testing their JS?
Intro | WHY Why Testing?
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, Monkey
tests..?
Intro | TERMINOLOGY Unit tests App Tests UI tests
Testing With Siesta Introduction
Intro | Testing with Siesta • runs in any browser
• is written in plain JS • is sandboxed by default A Siesta test…
Intro | Testing with Siesta • can do both UI
and unit testing • can be automated using PhantomJS or Selenium WebDriver • can detect leaked global variables A Siesta test…
Intro | Testing with Siesta describe('A simple Model test', function
(t) { t.it('Should do something', function(t) { // Test things t.expect(1).toBe(1); }); });
Unit Tests Red, Green, Refactor
Unit tests | Intro •Unit tests usually only involve “raw”
JS •Run very fast •Perfect for pre-commit hooks •Disable sandboxing if possible
Unit tests | Intro •Should be your #1 priority •Cover
your most important JS classes •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
UI tests | Intro Siesta Event Recorder
UI tests | Event recorder •Great for application tests •Records
user actions: clicks, types, drag drop •Exports actions to a Siesta test case •Can be used by a non-programmer •Big timesaver
UI tests | Event recorder Let’s try the recorder
UI tests | Intro Application test demo Testing the Siesta
UI with Siesta
UI tests | Monkey tests Monkey testing
UI tests | Monkey tests •Random UI testing •Clicks, drags
etc. in your UI •Finds unhandled exceptions •Free testing help. 0€
UI tests | Monkey tests Cost breakdown: $5 * 0
= 0 $5
Continuous Integration TeamCity, Code Coverage & Statistics
Continuous Integration | Intro •Bryntum uses TeamCity, Siesta integrates with
others (Jenkins…) •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
UI tests | 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 => 7 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 Testing a SalesForce UI
Rounding up | Links •bryntum.com/products/siesta •bryntum.com/docs/siesta •teamcity.bryntum.com/guest •browserstack.com/ •saucelabs.com/
Rounding up | Questions Questions? Twitter: @Bryntum