Slide deck from my Salesforce World Tour talk on JavaScript Unit Testing.

1. Salesforce World Tour
London May 21, 2015

2. Keir Bowden
CTO, BrightGen
@bob_buzzard
Speaker

3. Safe Harbor
Safe harbor statement under the Private Securities Litigation Reform Act of 1995:
This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties
materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or
implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking,
including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements
regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded
services or technology developments and customer contracts or use of our services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality
for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results
and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of intellectual property and other
litigation, risks associated with possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating
history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer
deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further
information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-Q for the
most recent fiscal quarter ended July 31, 2012. This documents and others containing important disclosures are available on the SEC Filings
section of the Investor Information section of our Web site.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available
and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that
are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.

4. Agenda
• Introduction
• Tools
• Visualforce
• Lightning Components
• Q & A

5. Introduction

6. Introduction
• Why write unit tests?
– Give confidence
– Reduce cost of bugs
– Produce testable code
– Promote refactoring

7. JavaScript on Salesforce Challenges
• No test context for client
– Changes aren’t rolled back
• Side effects:
– DOM manipulation
– Server calls

8. Techniques
• Write testable code
– Unobtrusive JavaScript
– Avoid anonymous functions
– Functional decomposition
• Functions to decide on action
• Functions to take the action
function redirectToURL(url) {
if (“#”===url.charAt(0)) {
window.location.hash=url;
} else if (“/”===url.charAt(0))
window.location.pathname=url;
}
....

9. Demo App
Github:
bobbuzz.me.uk/JSUTSF
Public Site:
Jobs:
bobbuzz.me.uk/1Ad25OG
Tests:
bobbuzz.me.uk/1PvhII3

10. Tools

11. QUnit
• Pure JavaScript Unit Test Framework
• Executes in-browser
• From the developers of jQuery
<apex:includeScript
value="{!$Resource.qunitJS}"/>
<apex:stylesheet
value="{!$Resource.qunitCSS}"/>
<div id="qunit"></div>
<div id="qunit-fixture"></div>
Test markup container

12. QUnit
• Module – group of tests
• Test – single test
• Assert – confirm behaviour
QUnit.module("JOBLIST", {
beforeEach: function(assert) {
// setup code
},
afterEach : function(assert) {
// teardown code
}
});
QUnit.test("Show Progress", function( assert ) {
jobCtrl.showProgress();
});
assert.equal(jobCtrl.progressCount, 1,
"Progress count is one");

13. Sinon.JS
• Pure JavaScript
• Works with any test framework
• Three elements:
– Spies – records execution, parameters
– Stubs – Spies + replace functions
– Mocks – Stubs + expected behaviour

14. Sinon Stub
this.searchStub = sinon.stub(jobCtrl,
"doSearch");
var jobCtrl={
doSearch : function(ev) {
// remote call to server
}
};
jobCtrl.doSearch(event);
doSearch : function() {
// sinon stub code
}
assert.equal(this.searchStub.callCount,1,
"search called once");
this.searchStub.restore();
doSearch : function(ev) {
// remote call to server
}
$('#searchbtn').on("click",
jobCtrl.doSearch);

15. Blanket.js
• Code coverage!
• Pure JavaScript
• Works with QUnit, Mocha and Jasmine
• JavaScript must be external
<apex:includeScript value="{!$Resource.blanketJS}"/>
<script src="{!$Resource.JobsJS}" data-cover="true"></script>

16. Blanket.js

17. Visualforce

18. Visualforce
• Dedicated test page
• Replicate markup as required
• Include JavaScript to be tested
• Can capture coverage
• Demo

19. Lightning Components

20. Challenges
• Components are isolated
• JavaScript in controller + helper
• Cannot capture coverage
• Markup is fixed
• How to trigger tests?

21. My Solution
• QUnit tests in helper function
• Controller method to execute helper function
• Lightning test application (equivalent to page)
• Tests executed via event
– Fired by application
– Handled by component under test
• Demo

22. Keir Bowden
CTO, BrightGen
@bob_buzzard
Q & A

23. Thank you