Automated Testing With Jasmine, PhantomJS and Jenkins
Post on 11-May-2015
18663 Views
Preview:
DESCRIPTION
Transcript
1
Automated Testing With Jasmine, PhantomJS &
JenkinsAisha Kaliel | Ronn Abueg
Drupalcon 2013 Portland
1
2May 2013
Agenda
1.Who we are2.Testing JS code and front-
end• Testing without the
browser• Continuous Integration
2
3May 2013
1.Who we are2.Testing JS code and front-
end• Testing without the
browser• Continuous Integration
o Listing the types of tests
o Looking at some test tools
o Writing and running tests
Agenda
3
4May 2013
Agenda
1.Who we are2.Testing JS code and front-
end• Testing without the
browser• Continuous Integration
o What is a headless browser
o Scripting with a headless browser
o Testing with a headless browser
4
5May 2013
Agenda
1.Who we are2.Testing JS code and front-
end• Testing without the
browser• Continuous Integration
o Deploying codeo Integrating testing with
buildso Review build results
5
6May 2013
Who are we?
Aisha Kalieldrupal: akaliel
Ronn Abueg drupal: ronnbottwitter: @ronnbot
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration
twitter: @workatplayfacebook: www.facebook.com/workatplaywebsite: www.workatplay.com
6
7May 2013
We work with Drupal...
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 7
8May 2013
And other CMS/frameworks
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 8
9May 2013
And other CMS/frameworks
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 9
10May 2013
Repetitive Testing: Why not automate?
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration
10
11May 2013
Why test in general
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration
11
12May 2013
Automated testing...
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration
• Saves time and money
• Improves accuracy
• Increases test coverage
• Does what manual testing cannot
• Helps developers and testers
• Improves team moral
• and continuous integration is the cornerstone of Agile development
12
13May 2013
1.Who we are2.Testing JS code and front-
end• Testing without the
browser• Continuous Integration
o Listing the types of tests
o Looking at some test tools
o Writing and running tests
Agenda
13
14May 2013
Types of tests
GUI
Unit
Service / Integration
Test Pyramid•concepted by Mike Cohn•higher level tests at the top•larger number of test below•high level tests can encompass many low level tests, e.g.ofor form test to pass, functional units must work
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 14
15May 2013
Tackling the testing pyramid
GUI
Unit
Service / Integration
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 15
automating browser
JS testing
16May 2013
Testing tools
• Selenium• Watir• Windmill• Mocha• QUnit• Jasmine• and etc.
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 16
automating browser
JS testing
17May 2013
Testing tools
• Selenium• Watir• Windmill• Mocha• QUnit• Jasmine
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 17
18May 2013
Comparison
Selenium
•Automates browsers
•Simulates user actions
•There's an IDE, a Firefox extension, that allows to record, edit, and debug tests
Jasmine
•Open-source testing framework for JavaScript
•Does not depend on DOM or any other JavaScript frameworks
•Unit tests your JS code
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 18
19May 2013
Why Jasmine?
• Runs anywhere Javascript can
• Does not intrude on the application
• Plays well with IDEs
• Encourages good testing principles
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 19
20May 2013
What is Jasmine?
• Behavior-driven development framework
• Does not require require a DOM, or depend on any other JavaScript frameworks
• Clean, obvious syntax
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 20
21May 2013
What is Jasmine?
• Behavior-driven development framework
• Does not require require a DOM, or depend on any other JavaScript frameworks
• Clean, obvious syntax
• Specialized version of test-driven development
• Focuses on the "desired behavior" of software
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 21
22May 2013
What is Jasmine?
• Behavior-driven development framework
• Does not require require the DOM, or depend on any other JavaScript frameworks
• Clean, obvious syntax
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 22
23May 2013
What is Jasmine?
• Behavior-driven development framework
• Does not require require a DOM, or depend on any other JavaScript frameworks
• Clean, obvious syntax
Still has access to the DOM!
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 23
24May 2013
What is Jasmine?
• Behavior-driven development framework
• Does not require require a DOM, or depend on any other JavaScript frameworks
• Clean, obvious syntax
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 24
25May 2013
Tackling the testing pyramid with Jasmine
GUI
Unit
Service / Integration
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 25
26May 2013
Tackling the testing pyramid with Jasmine
GUI
Unit
Service / Integration
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 26
27May 2013
Tackling the testing pyramid with Jasmine
GUI
Unit
Service / Integration
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 27
28May 2013
Jasmine Features
• Test suites/specs• Expectations• Matchers• Setup and teardown• Spies• Asynchronous Support
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 28
29May 2013
Feature to test: basic calculator
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 29
30May 2013
Basic calculator
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 30
31May 2013
Basic calculator
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 31
32May 2013
Basic calculator
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 32
33May 2013
Test the calculator: Suites
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 33
34May 2013
Test the calculator: Specs
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 34
35May 2013
Testing the calculator: Expectations
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 35
36May 2013
Feature: Matchers
• expect(x).toBe(y);
• expect(x).toEqual(y);
• expect(x).toMatch(/pattern/);
• expect(x).toBeDefined();
• expect(x).toBeUndefined();
• expect(x).toBeNull();
• expect(x).toBeTruthy();
• expect(x).toBeFalsy();
• expect(x).toContain(y);
• expect(x).toBeLessThan(y);
• expect(x).toBeGreaterThan(y);
• expect(x).toBeCloseTo(y, 0);
• expect(function(){ fn(); }).toThrow(e);
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 36
37May 2013
Feature: Negative Matchers
• expect(x).not.toBe(y);
• expect(x).not.toEqual(y);
• expect(x).not.toMatch(/pattern/);
• expect(x).not.toBeDefined();
• expect(x).not.toBeUndefined();
• expect(x).not.toBeNull();
• expect(x).not.toBeTruthy();
• expect(x).not.toBeFalsy();
• expect(x).not.toContain(y);
• expect(x).not.toBeLessThan(y);
• expect(x).not.toBeGreaterThan(y);
• expect(x).not.toBeCloseTo(y, 0);
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 37
38May 2013
Testing the calculator: Matchers
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 38
39May 2013
Testing the calculator: More specs!
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 39
40May 2013
Feature: Setup and Teardown
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 40
41May 2013
Testing the calculator: Setup
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 41
42May 2013
Testing the calculator: Spies
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 42
43May 2013
Testing the calculator with DOM tests
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 43
44May 2013
Testing the calculator: Nested describe blocks
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 44
45May 2013
Testing the calculator: Setup and Teardown
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 45
46May 2013
Feature: Asynchronous Support
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 46
47May 2013
Feature: Asynchronous Support
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 47
48May 2013
Feature: Asynchronous Support
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 48
49May 2013
Testing the calculator: Reporter
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 49
50May 2013
Testing the calculator: Reporter
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 50
51May 2013
Testing the calculator: Filtering the Reporter
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 51
52May 2013
Running the test page without a browser
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 52
53May 2013
Agenda
1.Who we are2.Testing JS code and front-
end• Testing without the
browser• Continuous Integration
o What is a headless browser
o Scripting with a headless browser
o Testing with a headless browser
53
54Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration May 2013
What is a headless browser
• Web browser without a GUI
• Renders web pages
• Outputs to non-humans i.e. other software
• Useful for:o testingo parsingo screen capture
54
55Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration May 2013
Enter the PhantomJS• Headless WebKit
• Scriptable with JavaScript/CoffeeScript
• Support for various web standards:o DOM handlingo CSS selectoro JSONo Canvaso SVG
55
56May 2013
PhantomJS basic how toCreate a script: hello.js
console.log('Hello, DrupalCon Portland!');
phantom.exit();
Run script in the command line
phantomjs hello.js
Output
Hello, DrupalCon Portland!
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 56
57May 2013
PhantomJS modulesWebPageA WebPage object encapsulates a web page.
SystemA set of functions to access system-level functionality.
FileSystemA set of API functions available to access files and directories.
WebServerUsing an embedded web server module called Mongoose, PhantomJS script can start a web server.
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 57
58May 2013
PhantomJS basic how toPage Loading: loadpage.js
var page = require('webpage').create();
page.open('http://portland2013.drupal.org', function () {
page.render('drupalcon.png');
phantom.exit();
});
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 58
59May 2013
PhantomJS basic how toPage Loading with arguments
var page = require('webpage').create(),
system = require('system');
page.open(system.args[1], function (status) { if (status == 'success') { console.log('Loaded the address: ' + system.args[1]); } phantom.exit(); });
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 59
60May 2013
PhantomJS basic how toPage Loading with arguments
var page = require('webpage').create(),
system = require('system');
page.open(system.args[1], function (status) { if (status == 'success') { console.log('Loaded the address: ' + system.args[1]); } phantom.exit(); });
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 60
61May 2013
PhantomJS basic how toPage Loading with arguments
var page = require('webpage').create(),
system = require('system');
page.open(system.args[1], function (status) { if (status == 'success') { console.log('Loaded the address: ' + system.args[1]); } phantom.exit(); });
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 61
62May 2013
PhantomJS basic how toPage Loading with arguments
var page = require('webpage').create(),
system = require('system');
page.open(system.args[1], function (status) { if (status == 'success') { console.log('Loaded the address: ' + system.args[1]); } phantom.exit(); });
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 62
63May 2013
PhantomJS basic how toRun script in the command line
phantomjs loadpage.js http://www.google.com
Output
Loaded the address: http://www.google.com
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 63
64May 2013
PhantomJS basic how toCode Evaluation
var page = require('webpage').create();
page.open(url, function (status) {
var title = page.evaluate(function () {
return document.title;
}); console.log('Page title is ' + title); });
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 64
65May 2013
Running Jasmine with PhantomJS
Github: phantomjs / examples / run-jasmine.jsLocated at: https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 65
66May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 66
67May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 67
68May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 68
69May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 69
70May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 70
71May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 71
72May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 72
73May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 73
74May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 74
75May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 75
76May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 76
77May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 77
78May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 78
79May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 79
80May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 80
81May 2013
Running Jasmine with PhantomJSFrom https://github.com/ariya/phantomjs/blob/master/examples/run-jasmine.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration
...
...
...
81
82May 2013
PhantomJS featuresHeadless web testingLightning-fast testing without the browser with various test frameworks.
Page automationAccess and manipulate web pages with the standard DOM API, or with usual JavaScript libraries.
Screen captureProgrammatically capture web contents including CSS, SVG and Canvas.
Network monitoringAutomate performance analysis, track page loading and export as standard HAR format.
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 82
83May 2013
PhantomJS custom modules (v1.7)RequireUsers can reference their own modules from the file system using require function.
General usage
var server = require('webserver').create();
var Awesome = require('MyAwesomeModule');
Awesome.do();
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 83
84
CI
May 2013
Lets integrate it with Jenkins
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 84
85May 2013
Agenda
1.Who we are2.Testing JS code and front-
end• Testing without the
browser• Continuous Integration
o Deploying codeo Integrating testing with
buildso Review build results
85
86May 2013
Meet Jenkins
• Leading open-source Continuous Integration server
• Built with Java
• Plug-in support
• RSS/E-mail/IM support
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 86
87May 2013
Jenkins in action - dashboard
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 87
88May 2013
Jenkins in action - project
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 88
89May 2013
Jenkins in action - build
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 89
90May 2013
Jenkins in action - build detail
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 90
91May 2013
Deploying code - console output of build
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 91
92May 2013
PhantomJs & Jasmine with XML
Github: detro / phantomjs-jasminexml-exampleLocated at: https://github.com/detro/phantomjs-jasminexml-example
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 92
93May 2013
Jasmine Reporter Plugin
Github: ../ test / lib / jasmine-reportersLocated at: https://github.com/detro/phantomjs-jasminexml-example/tree/master/test/lib/jasmine-reporters
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 93
94May 2013
Jasmine Reporter Plugin
Github: ../ test / lib / jasmine-reportersLocated at: https://github.com/detro/phantomjs-jasminexml-example/tree/master/test/lib/jasmine-reporters
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 94
95May 2013
PhantomJS XML Runner
Github: ../ test / phantomjs_jasminexml_runner.jshttps://github.com/detro/phantomjs-jasminexml-example/blob/master/test/phantomjs_jasminexml_runner.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 95
96May 2013
PhantomJS XML Runner
Github: ../ test / phantomjs_jasminexml_runner.jshttps://github.com/detro/phantomjs-jasminexml-example/blob/master/test/phantomjs_jasminexml_runner.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 96
97May 2013
PhantomJS XML Runner
Github: ../ test / phantomjs_jasminexml_runner.jshttps://github.com/detro/phantomjs-jasminexml-example/blob/master/test/phantomjs_jasminexml_runner.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 97
98May 2013
PhantomJS XML Runner
Github: ../ test / phantomjs_jasminexml_runner.jshttps://github.com/detro/phantomjs-jasminexml-example/blob/master/test/phantomjs_jasminexml_runner.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 98
99May 2013
PhantomJS XML Runner
Github: ../ test / phantomjs_jasminexml_runner.jshttps://github.com/detro/phantomjs-jasminexml-example/blob/master/test/phantomjs_jasminexml_runner.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 99
100May 2013
PhantomJS XML Runner
Github: ../ test / phantomjs_jasminexml_runner.jshttps://github.com/detro/phantomjs-jasminexml-example/blob/master/test/phantomjs_jasminexml_runner.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 100
101May 2013
PhantomJS XML Runner
Github: ../ test / phantomjs_jasminexml_runner.jshttps://github.com/detro/phantomjs-jasminexml-example/blob/master/test/phantomjs_jasminexml_runner.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 101
102May 2013
PhantomJS XML Runner
Github: ../ test / phantomjs_jasminexml_runner.jshttps://github.com/detro/phantomjs-jasminexml-example/blob/master/test/phantomjs_jasminexml_runner.js
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 102
103May 2013
Running PhantomJS in Jenkins: configuration
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 103
104May 2013
Running PhantomJS in Jenkins: Console Output
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 104
105May 2013
Publishing test results in Jenkins: configuration
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 105
106May 2013
Publishing test results in Jenkins: configuration
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 106
107May 2013
Publishing test results in Jenkins: Console Output
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 107
108May 2013
Review build and test results
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 108
109May 2013
Review build and test results
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 109
110May 2013
Review test results
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 110
111May 2013
Review test results
Who we are | Testing JS Code & Front-End | Testing without the Browser | Continuous Integration 111
112May 2013
Agenda
1.Who we are2.Testing JS code and front-
end• Testing without the
browser• Continuous Integration
112
113May 2013
Agenda
1.Who we are2.Testing JS code and front-
end• Testing without the
browser• Continuous Integration
o Wrote and ran tests in Jasmine
o We are able to do various types of testsautomatically
o This is more accurate than manual testing
113
114May 2013
Agenda
1.Who we are2.Testing JS code and front-
end• Testing without the
browser• Continuous Integration
o Executed Jasmine tests via PhantomJS
o The tests can be ran by non-humans
o This saves us resources
114
115May 2013
Agenda
1.Who we are2.Testing JS code and front-
end• Testing without the
browser• Continuous Integration
o Added tests execution during builds on Jenkins
o Reviewed test results in Jenkins after builds
o Allows us to be more agile
115
117May 2013
Thank you!
Evaluate this session at:
portland2013.drupal.org/scheduleEnjoy the rest of
Drupalcon 2013 Portland
117
top related