�ݺ�ߣ

JavaScript Is Not a ToyIt’s Time it was TestedDevelopersJames Hatton : salesforce.comAlexis Williams: salesforce.com

Safe HarborSafe 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 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, 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-K for the most recent fiscal year ended January 31, 2010. This documents and others 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 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.

AgendaThe evolution of JavaScriptTools to help you test:Jasmine by Pivotal Labs YUI Test by Yahoo!Demos. How to use these tools with the force.com platformQuestions & Answers

Session ObjectiveBy the end of this session you will be ready to get started with Jasmine and YUI Test inside your force.com environment.

It’s not the ‘90s anymoreIn the past only trivial tasks were delegated to JavaScriptToday’s applications have a growing dependency on JavaScript and asynchronous services

JavaScript is no longer a toy language

We have tools nowJasmine test framework by Pivotal LabsYUI test framework by Yahoo

JasmineJasmine is a behavior-driven development framework for testing your JavaScript code. It does not depend on any other JavaScript frameworks. It has a clean, obvious syntax so that you can easily write tests.

What is BDD?Behavior Driven Development“BDD is a second-generation, outside-in, pull-based, multiple-stakeholder, multiple-scale, high-automation, agile methodology.”Huh?

Hold on what is BDD?“A practice of writing test cases in a natural language that non-programmers can read.”

Examplefunction helloWorld() { return "Hello, World!";}describe('helloWorld()', function() {it('says hello', function() {expect(helloWorld()).toEqual("Hello, World!"); });});

Another Examplefunction copyToDiv() {var source = document.getElementById(‘source’);var content = document.getElementById(‘content’);content.innerHTML = source.innerHTML;}describe(’copyToDiv()', function() {it(’copies input data to content', function() {copyToDiv();var content = document.getElementById(‘content’).innerHTMLexpect(content).toEqual(‘source data’); });});

Tests are called “Specs”You tell Jasmine about a spec with a call to it() with a description string and the function.

The string is a description of a behavior that you want your production code to exhibit; it should be meaningful to you when reading a report.it('should increment a variable', function () { varfoo = 0; foo++; });

ExpectationsWithin your spec you will express expectations about the behavior of your application code. This is done using the expect() function.function increment(foo) { returnfoo++;}describe('increment()', function() { it('should increment a variable', function() {varfoo = 0; expect(increment(foo)).toEqual(1); });});

SuitesSpecs are grouped in Suites. Suites are defined using the global describe() function.describe('Calculator', function () { it('can add a number', function() { ... }); it(’multiply some numbers', function() { ... }); });

Expectation MatchersJasmine has several built-in matchers. For example:expect(x).toEqual(y); expect(x).toBeNull(); expect(x).toContain(y); expect(x).toBeLessThan(y); expect(x).toBeGreaterThan(y); expect(fn).toThrow(e); Each matcher’s criteria can be inverted by prepending .not

Custom MatchersJasmine includes a small set of matchers that cover many common situations. However you can write custom matchers when you want to assert a more specific sort of expectation. Custom matchers help to document the intent of your specs, and can help to remove code duplication in your specs.

Custom Matchers – An ExampleTo add the matcher to your suite, call this.addMatchers() from within a beforeEach or block. beforeEach(function() { this.addMatchers({ toBeVisible: function() {return this.actual.isVisible();} }); });

Custom MatchersbeforeEach(function() {this.addMatchers({toBeACar: function() { return this.actual.hasWheels() && this.actual.hasEngine() && this.actual.hasSteeringWheel(); } });});describe(‘car’, function() {it(‘is a car’, function() {expect(car).toBeACar(); });});

beforeEachA suite can have a beforeEach() declaration. It takes a function that is run before each spec. For example:describe('some suite', function () { varsuiteWideFoo; beforeEach(function () { suiteWideFoo = 1; }); it('should equal bar', function () { expect(suiteWideFoo).toEqual(1); }); });

beforeEachRunner beforeEach() functions are executed before every spec in all suites, and execute BEFORE suite beforeEach() functions. For example:varrunnerWideFoo = []; beforeEach(function () { runnerWideFoo.push('runner'); });describe('some suite', function () {beforeEach(function () { runnerWideFoo.push('suite'); }); it('should equal bar', function () { expect(runnerWideFoo).toEqual(['runner', 'suite']); }); });

afterEachSimilarly, there is an afterEach() declaration. It takes a function that is run after each spec. For example:describe('some suite', function () { varsuiteWideFoo = 1; afterEach(function () { suiteWideFoo = 0; }); it('should equal 1', function() { expect(suiteWideFoo).toEqual(1); }); it('should equal 0 after', function(){ expect (suiteWideFoo).toEqual(0); };});

afterEachvarrunnerWideFoo = [];afterEach(function () {runnerWideFoo.push('runner');});describe('some suite', function () {afterEach(function () {runnerWideFoo.push('suite'); });it('should be empty', function () {expect(runnerWideFoo).toEqual([]); });it('should be populated after', function () {expect(runnerWideFoo).toEqual(['suite', 'runner']); };});

Spies!Spies allow you to “spy” on the function being called granting far more visibility into its behavior then can be achieved by inspecting the return value.

How to spy on your codefunction Hostess(name) {this.name = name;this.getName = function() { return name; };this.greetParty = function() { return “My name is “ + this.getName() + “ please follow me” };//..it(‘uses the name’, function() {var hostess = new Hostess(‘Janet’); spyOn(hostess, ‘getName’);expect(hostess.greetParty()).toMatch(‘My name is Janet please follow me’);expect(hostess.getName).toHaveBeenCalled();});

Spy-Specific MatchersThere are spy-specific matchers that are very handy.expect(x).toHaveBeenCalled()expect(x).toHaveBeenCalledWith(arguments)expect(x).not.toHaveBeenCalled()expect(x).not.toHaveBeenCalledWith(arguments)

Useful PropertiesSpies have some useful properties:callCountmostRecentCall.argsargsForCall[i]Spies are automatically removed after each spec. They may be set in the beforeEach function.

Spy Example 2varKlass = function () { }; Klass.staticMethod = function (arg) { return arg; }; Klass.prototype.method = function (arg) { return arg; };Klass.prototype.methodWithCallback = function (callback) { return callback('foo'); };

Spy Example 2 Continued…it('should spy on a static method of Klass', function() { spyOn(Klass, 'staticMethod'); Klass.staticMethod('foo argument'); expect(Klass.staticMethod).toHaveBeenCalledWith('foo argument'); });

Spy Example 2 Continued…it('should spy on an instance method of a Klass', function() { varobj = new Klass(); spyOn(obj, 'method'); obj.method('foo argument'); expect(obj.method).toHaveBeenCalledWith('foo argument'); var obj2 = new Klass(); spyOn(obj2, 'method'); expect(obj2.method).not.toHaveBeenCalled(); });

Spy Example 2 Continued…it('should spy on Klass.methodWithCallback', function() { var callback = jasmine.createSpy(); new Klass().methodWithCallback(callback);expect(callback).toHaveBeenCalledWith('foo');});

Spy Example 3varKlass = function () { }; varKlass.prototype.asyncMethod = function (callback) { someAsyncCall(callback); };

Spy Example 3 Continued…it('should test async call') {spyOn(Klass, 'asyncMethod');var callback = jasmine.createSpy();Klass.asyncMethod(callback);expect(callback).not.toHaveBeenCalled();varsomeResponseData = 'foo'; Klass.asyncMethod.mostRecentCall.args[0](someResponseData);expect(callback).toHaveBeenCalledWith(someResponseData);});

Asynchronous SpecsImagine you need to make a call that is asynchronous - an AJAX API, event callback, or some other JavaScript library. That is, the call returns immediately, yet you want to make expectations ‘at some point in the future’ after some magic happens in the background.Jasmine allows you to do this with runs(), waits() and waitsFor() blocks.

Asynchronous Specsdescribe('Spreadsheet', function() { it('should calculate the total asynchronously', function () { var spreadsheet = new Spreadsheet(); spreadsheet.fillWith(lotsOfFixureDataValues()); spreadsheet.asynchronouslyCalculateTotal(); waitsFor(function() { return spreadsheet.calculationIsComplete(); }, "Spreadsheet calculation never completed", 10000); runs(function () { expect(spreadsheet.total).toEqual(123456); }); });});

YUI Test – What is it?YUI Test is a test driven development framework for testing your JavaScript code. It does not depend on any other JavaScript frameworks. It allows you to plug into any other frameworks: Dojo, jQuery, Prototype…It has a clean JSON like syntax many of us are familiar with already

YUI Test – What are the Benefits?Reduces overall ramp up timeFamiliar JSON like syntaxTests cases are easy to createProvides setup and tear down functionalityWriting tests (unit) is easyExplicitly indicates test outcomesGroups together test case statistics

Getting Started with YUI TestCreate HTML pageInclude required resources: Java script and CSSCreate test caseAdd unit testsAdd test cases to test suiteOpen in web browser to run test suite and view results

Test Cases and Unit Tests {Test Methods}Test Case is comprised of unit testsUnit tests exercise small, isolated units of codeUnit tests have expected input and outputsThe test case will present the number of passed and failed unit tests

Creating a Test Case and Test Methods Pt. 1Create a new instance of the TestCaseAny method prefixed with lower case test is considered a unit test to runAny method not defined already or prefixed with test is considered a helper methodBuilt in methods:Set up: set up data that will be consumed in test methodsTear down: construct to tear down data setup for test methods

Creating a Test Case and Test Methods Pt. 2

Test Method Assertions Pt. 1Equality AssertionsareEqual() and areNotEqual(): both accept 3 arguments: expected value, actual value, and optional failure messageAssert.areEqual(5, 5); //passesAssert.areEqual(5, "5"); //passesAssert.areEqual(5, 6, "Five was expected."); //failsSameness AssertionsareSame() and areNotSame(): same argument structure like equals, but uses different comparison operator (===)Assert.areSame(5, "5"); //failsAssert.areNotSame(5, 6); //passesAssert.areSame(5, 6, "Five was expected."); //fails

Test Method Assertions Pt. 2Data Type Assertionstest the data type of variables: accepts 2 arguments, the variable to test, and an optional error message. Assert.isString("Hello world"); //passesAssert.isNumber(1); //passesAssert.isArray([]); //passesAssert.isObject([]); //passesAssert.isFunction(function(){}); //passesAssert.isBoolean(true); //passesAssert.isObject(function(){}); //passes

Test Method Assertions Pt. 3Special Value Assertionsdesigned to test for the following special values: true, false, NaN, null, and undefined. Accepts 2 arguments again: the variable to test, and an optional error message.Assert.isFalse(false); //passes Assert.isNaN(5 / "5"); //passesAssert.isNull(null); //passesAssert.isUndefined(undefined); //passesForced FailuresForced failure you can optionally pass a message into

Getting Test Cases Ready to Run Pt. 1Create new instance of TestSuiteAdd testCases to TestSuiteCreate new instance of TestLoggerAdd the test suite to TestLoggerRun the test suite with TestRunner when the DOM is ready

Getting Test Cases Ready to Run Pt. 2

Enter The Complexities – Browser EnvironmentDependencies upon page eventsExecution types:SynchronousAsynchronousDifferent behaviors exhibited per browser

Simulating User Actions {Mouse & Keyboard}Each event is fired by a corresponding method on UserAction that accepts two arguments: the target of the event and an optional object specifying additional information for the eventYAHOO.util.UserAction object provides methods to simulate basic user events involving the keyboard and mouse

Simulating Mouse ActionsSeven mouse events that can be simulated: click, dblclick, mousedown, mouseup, mouseover, mouseout, mousemovevar element = document.getElementById("myDiv");//simulate a click Alt key downYAHOO.util.UserAction.click(element, { altKey: true});//simulate a double click with Ctrl key downYAHOO.util.UserAction.dblclick(element, { ctrlKey: true });

Simulating Keyboard ActionsThree key events that can be simulated: keyup, keydown, keypressKey events also support the ctrlKey, altKey, shiftKey, and metaKey event propertiesvar element = document.getElementById("myDiv");//simulate a keydown on the A keyYAHOO.util.UserAction.keydown(element, { keyCode: 97 });//simulate a keyup on the A keyYAHOO.util.UserAction.keyup(element, { keyCode: 97 });

Asynchronous Testing – Wait Pt. 1YUI Test allows you to pause a currently running test and resume either after a set amount of time or at another designated timeThe TestCase object has a method called wait(). When wait() is called, the test immediately exits (meaning that any code after that point will be ignored) and waits for a signal to resume the test.

Asynchronous Testing – Wait Pt. 2A test may be resumed after a certain amount of time by passing in two arguments to wait(): a function to execute and the number of milliseconds to wait before executing the function (similar to using setTimeout()). The function passed in as the first argument will be executed as part of the current test (in the same scope) after the specified amount of time.

Asynchronous Testing – Wait Pt. 3 Example of using wait with a timer

Real Life Example {Ghost Text} Pt. 1Need: when user loads a VF page they are presented ghost text (grey) in description field. The text should disappear when they click in the field, text color should be black, and reappear if they don’t add any text with text color back to greyTranslation: create function to populate text and erase textFunction: Add ghost text to fieldRemove ghost text from fieldAdd ghost text to field if needed

Real Life Example {Ghost Text} Pt. 2Render ghost text when Description field is null

Real Life Example {Ghost Text} Pt. 3Remove ghost text when clicking in Description field

Real Life Example {Ghost Text} Pt. 4

Working with the Results Test LoggerUse the test logger to output the resultsvaroLogger = new YAHOO.tool.TestLogger();YAHOO.tool.TestRunner.run();

Working with the Results Test Reporter Pt. 1Use the test reporter to create a form that posts the results to a specific URL: results - the serialized results object.useragent - the user-agent string of the browser.timestamp - the date and time that the report was sent.One way direction – no return processed from serverDoes not cause you to navigate away from pagevaroReporter = new YAHOO.tool.TestReporter("http://www.yourserver.com/path/to/target");oReporter.report(results);

Working with the Results Test Reporter Pt. 2Custom fieldsCustom fields can be added to the results report using the addField() methodCustom fields are appended to the standard fields postedoReporter.addField("User_Story_c", "a0lB00000004IkV");oReporter.addField("Test_Case__c", "a07B0000000DlSEIA0");

Working with the Results Test Reporter Pt. 3Two serialization formats for the results objects: XML and JSONXML is the default formatvaroReporter = new YAHOO.tool.TestReporter("https://na1.salesforce.com/apex/processYIUTest", YAHOO.tool.TestFormat.JSON);

ResourcesJasmine: http://pivotal.github.com/jasmine/YUI Test: http://developer.yahoo.com/yui/yuitest/

�ݺ�ߣ

Java Script Isn\'t a Toy Anymore

More Related Content

Java Script Isn\'t a Toy Anymore

Editor's Notes