AtlasCamp 2011 - Five Strategies to Accelerate Plugin Development

Five Strategies to Accelerate Plugin Dev Lessons from Speakeasy Don Brown Integration Architect, Atlassian

Five Strategies Discover your plugin with Speakeasy Define interactions with page objects Optimize your dev loop with the SDK Reuse functionality with AUI Encourage feedback

1. Discover your plugin with Speakeasy

The #1 time waster is not building the plugin poorly, but is building the wrong plugin Me, channeling Eric Ries ” “

Example: Inline Commenting Get stats on how often people comment. Ask heavy comment authors their gripes. Slowness of commenting causing fewer comments and annoyed users Edit a few heavily commented pages and see if the linked numbers help or hurt Users want to see number of comments on a line Look through last 100 comments, note cause and use of quotes Users want to comment on specific lines in on a page Test Assumption

Social Validation Speakeasy Prototype Plugin

Examine a recent plugin idea and try to identify your assumptions and how you might test them ” “

2. Define Interactions with Page Objects

Overly Simplifying Testing Unit Testing Where? Same VM Awesome for? Method validation Functional Testing Where? External VM Awesome for? Use case validation

Selenium the Ugly waitForEntityRowToBeAdded(); // check entity row has been created assertThat.textPresent("Schultz"); assertThat.textPresent("brown"); assertEquals("Delete", client.getText("link=Delete")); // now we delete client.click("link=Delete"); client.waitForAjaxWithJquery(); client.click("//div[@id='delete-application-link-dialog']/div[2]/div[2]/button"); client.waitForAjaxWithJquery(); client.click("//div[@id='delete-application-link-dialog']/div[2]/div[2]/button");

Reminds Me of These Days: if(request.getParameter("action") != null){ String bookname=request.getParameter("bookname"if(request.getParameter("action") != null){ String bookname=request.getParameter("bookname"); String author=request.getParameter("author"); stmt.executeUpdate("insert into books_details(book_name, author) values('"+bookname+"','"+author+"')"); rst=stmt.executeQuery("select * from books_details"); %> <html> <body> <center> <h2>Books List</h2>

JSP Solution: Data Access Objects Selenium Solution: Page Objects

Boldly go where no functional test has gone before…

Use Now! JIRA 4.x, 5.0 Confluence 3.x, 4.x Bamboo 3.3 FishEye/Crucible, coming soon

Take a look at the Atlassian page object docs and try to write a hello world test for your plugin ” “

3. Optimize the Dev Loop with the SDK

All About the Gap Gap between edit and view Productivity

Edit -> Refresh js/vm, hotswap changes Gap between edit and view Productivity

Edit -> ‘pi’ -> Refresh java changes Gap between edit and view Productivity

Edit -> CTRL-C -> atlas-run WEB-INF/lib changes Gap between edit and view Productivity

Run Simultaneously Switch between products Terminal tab per instance

Quickly Spot Errors In your .bashrc file export MAVEN_COLOR=true

Track how many times you alt-tab away from development in a day and try to decrease it ” “

Play with the AUI sandbox and try out a few components ” “

JIRA Mobile Connect Automated crash reporting as a JIRA issue Message reporters directly, attached to the issue

JIRA Issue Connector Embeddable JavaScript to allow users to raise issues for your plugin

Add JIRA Issue Connector to as an optional feature to your plugin for dogfooding ” “

Ruthlessly eliminate unnecessary weight from the start “ ” ”

The JIRA Studio Problem How to allow plugins without breaking Studio?

Plugins Missing Potential Lots to know just to get started Java, Maven, XML, tons of APIs, libraries, and frameworks Lots of things to break API changes, memory leaks, runaway functions Limited deployment options Not safe for Studio

Speakeasy is great. . . Easy to get started Just a zip with some JavaScript Safe to experiment Per user allowed Easy to deploy using Git

But. . . Only supports client-side JavaScript DOM as the API is incredibly brittle Very different to “real” plugins

2012 Project: Remote Plugins What if plugins ran on your server like Facebook Applications? What if all you had to install in JIRA Studio was a single XML descriptor file? What if you could write a plugin that could be deployed for JIRA Studio or custom instances without changes?

Let me know. . . Are you interested in deploying plugins for our JIRA Studio customers? Would you like to use this capability for custom instances? Would you be interested in having early access? Contact me: don@atlassian.com or @mrdonbrown

Body Level One Body Level One Body Level Two Body Level Two Body Level One Body Level Two Body Level One Body Level One Body Level Two Body Level Two Body Level One Body Level Two

Enter take-away information here, short enough to be tweeted & retweeted. Move the closing quotation to the end of the sentence manually. “ ”

Body Level One Body Level One Body Level Two Body Level Two Body Level One Body Level Two

References Speakeasy Page Objects – Coming soon Plugin SDK Multiple products Colorization Atlassian User Interface (AUI) JIRA Mobile Connect JIRA Issue Connector

AtlasCamp 2011 - Five Strategies to Accelerate Plugin Development

More Related Content

What's hot

Viewers also liked

Similar to AtlasCamp 2011 - Five Strategies to Accelerate Plugin Development

Recently uploaded

AtlasCamp 2011 - Five Strategies to Accelerate Plugin Development