Google Testing Blog

Testing on the Toilet: Truth: a fluent assertion framework

Friday, December 19, 2014

by Dori Reuveni and Kurt Alfred Kluever

This article was adapted from a Google Testing on the Toilet (TotT) episode. You can download a printer-friendly version of this TotT episode and post it in your office. As engineers, we spend most of our time reading existing code, rather than writing new code.Truth is an open source, fluent testing framework for Java designed to make your test assertions and failure messages more readable.assertEquals("March", monthMap.get(3)); // JUnit assertThat(monthMap).containsEntry(3, "March"); // TruthAnother benefit of Truth over JUnit is the addition of useful default failure messagesImmutableSet<String> colors = ImmutableSet.of("red", "green", "blue", "yellow"); assertTrue(colors.contains("orange")); // JUnit assertThat(colors).contains("orange"); // TruthJUnit will not provide a useful failure messageTruth will provide a clear and concise failure messageAssertionError: <[red, green, blue, yellow]> should have contained <orange>Truth already supports specialized assertions for most of the common JDK typesTruth is also user-extensible: you can easily write a Truth subject to make fluent assertions about your own custom typesTruth's goal is not to replace JUnit assertions, but to improve the readability of complex assertions and their failure messagesTo get started with Truth, check outhttp://google.github.io/truth/

10 comments

GTAC 2014 Wrap-up

Thursday, December 04, 2014

by Anthony Vallone on behalf of the GTAC Committee GTAC 2014Google Kirkland officeArgentina, Australia, Canada, China, many European countries, India, Israel, Korea, New Zealand, Puerto Rico, Russia, Taiwan, and many US states

Adobe, American Express, Comcast, Dropbox, Facebook, FINRA, Google, HP, Medidata Solutions, Mozilla, Netflix, Orange, and University of Waterlooslides and video recordings

TwitterGoogle+

speakersGoogle Testing Blog

No comments

Protractor: Angular testing made easy

Sunday, November 30, 2014

By Hank Duan, Julie Ralph, and Arif Sukoco in Seattle protractortest.org

You don’t need to add waits or sleeps to your test. Protractor can communicate with your AngularJS app automatically and execute the next step in your test the moment the webpage finishes pending tasks, so you don’t have to worry about waiting for your test and webpage to sync.

It supports Angular-specific locator strategies (e.g., binding, model, repeater) as well as native WebDriver locator strategies (e.g., ID, CSS selector, XPath). This allows you to test Angular-specific elements without any setup effort on your part.

It is easy to set up page objects. Protractor does not execute WebDriver commands until an action is needed (e.g., get, sendKeys, click). This way you can set up page objects so tests can manipulate page elements without touching the HTML.

It uses Jasmine, the framework you use to write AngularJS unit tests, and Javascript, the same language you use to write AngularJS apps.

1) Set up environment npm install -g protractorwebdriver-manager update & webdriver-manager starthttp://localhost:44442) Write your test// It is a good idea to use page objects to modularize your testing logic var angularHomepage = { nameInput : element(by.model('yourName')), greeting : element(by.binding('yourName')), get : function() { browser.get('index.html'); }, setName : function(name) { this.nameInput.sendKeys(name); } }; // Here we are using the Jasmine test framework // See http://jasmine.github.io/2.0/introduction.html for more details describe('angularjs homepage', function() { it('should greet the named user', function(){ angularHomepage.get(); angularHomepage.setName('Julie'); expect(angularHomepage.greeting.getText()). toEqual('Hello Julie!'); }); });exports.config = { seleniumAddress: 'http://localhost:4444/wd/hub', specs: ['testFolder/*'], multiCapabilities: [{ 'browserName': 'chrome', // browser-specific tests specs: 'chromeTests/*' }, { 'browserName': 'firefox', // run tests in parallel shardTestFiles: true }], baseUrl: 'http://www.angularjs.org', };protractor conf.js1 test, 1 assertions, 0 failureshttp://angular.github.io/protractor/#/tutorial

1 comment

GTAC 2014 is this Week!

Monday, October 27, 2014

by Anthony Vallone on behalf of the GTAC Committee speaker profileslive stream pageupdated parking information

5 comments

Testing on the Toilet: Writing Descriptive Test Names

Thursday, October 16, 2014

by Andrew Trenk This article was adapted from a Google Testing on the Toilet (TotT) episode. You can download a printer-friendly version of this TotT episode and post it in your office. How long does it take you to figure out what behavior is being tested in the following code? @Test public void isUserLockedOut_invalidLogin() { authenticator.authenticate(username, invalidPassword); assertFalse(authenticator.isUserLockedOut(username)); authenticator.authenticate(username, invalidPassword); assertFalse(authenticator.isUserLockedOut(username)); authenticator.authenticate(username, invalidPassword); assertTrue(authenticator.isUserLockedOut(username)); }You probably had to read through every line of codehow long would it take you to figure out what behavior is being tested if the test had this name?isUserLockedOut_lockOutUserAfterThreeInvalidLoginAttempts
You should now be able to understand what behavior is being tested by reading just the test namePutting both the scenario and the expected outcome in the test name has several other benefits: If you want to know all the possible behaviors a class has, all you need to do is read through the test names in its test classBy giving tests more explicit names, it forces you to split up testing different behaviors into separate testsThe exact behavior being tested might not always be clear from the test codeYou can easily tell if some functionality isn’t being testedWhen a test fails, you can immediately see what functionality is broken without looking at the test’s source codeshouldLockOutUserAfterThreeInvalidLoginAttemptsMake sure test names contain both the scenario being tested and the expected outcome

4 comments

Testing Blog

Testing on the Toilet: Truth: a fluent assertion framework

GTAC 2014 Wrap-up

Protractor: Angular testing made easy

GTAC 2014 is this Week!

Testing on the Toilet: Writing Descriptive Test Names

Labels

Archive

Feed