This document discusses using Behavior Driven Development (BDD) for writing plugins. BDD involves having conversations to specify desired behavior using a ubiquitous language. It results in executable specifications that are safer and easier to test. The document proposes applying consumer-driven contracts - where Atlassian runs tests provided by plugin developers to check compatibility. This allows plugin developers to negotiate integration contracts through committed tests and renegotiate when requirements change.

2. BDD for plugin writers
... and giving your tests to Atlassian to run?!
Josh Graham
SaaS Architect, Atlassian
jgraham@atlassian.com
@delitescere 2

3. Plugins are awesome
3

4. Plugins are challenging
4

5. Plugins are rewarding
5

6. Easier
6

7. Safer
7

8. BDD
Behavior Driven Development
8

10. Overheard
“ BDD
=
TDD
+
”
natural domain language
#atlascamp @delitescere
10

11. Overheard
“ BDD
=
Conversations that
create software
”
#atlascamp @delitescere
11

12. Outside-in
12

13. Collaboration
QA
Developer
Business Owner User
13

14. Stakeholders
• Devs • other systems, units of
code...
• BAs
• QAs
• Business Sponsors
• Tech Writers
• Users
• Support 14

15. “ BDD is as much about the interactions between the
various people in the project as it is about the
”
outputs of the development process
Dan North, BDDiddy
15

16. “ If you’re not having conversations, you’re not
doing BDD.
”
Liz Keogh, BDDiva
16

17. Traceability
class Issue {
public Issue transition(Action action) {
currentState = workflow.transition(this, action);
}
}
Given an issue exists
And that issue is in the Open state
When I perform the Close action on that issue
Then that issue is in the Closed state 17

18. Business Outcomes
18

19. Plugin Developers
• Executable specification of system behavior
• Easily find regressions
• Test forward / backward compatibility
• Atlassian can run your tests?!
19

20. 20

21. BDD
• Given / When / Then
• Abstract
• Domain’s ubiquitous language
• Page Objects (if available)
• HTML
• A result of conversations
21

22. Consumers rule!
• Consumer-Driven Contracts –
Ian S. Robinson
• A new approach to integration
• Apply to plugins
• Atlassian runs your tests?!
22

23. The Contract
23

24. Sharing a contract repo
Atlassian Contract Your Plugin
.git .git .git
submodule submodule

25. Commit tests
Atlassian Contract Your Plugin
.git .git .git
submodule submodule

26. Negotiate contract
Atlassian Contract Your Plugin
.git .git .git
submodule submodule

27. Check contract violation
Atlassian Contract Your Plugin
.git .git .git
submodule submodule

28. Commit changed tests
Atlassian Contract Your Plugin
.git .git .git
submodule submodule

29. Renegotiate contract
Atlassian Contract Your Plugin
.git
.git .git
submodule submodule

30. Custom plugins?
30

31. Overheard
“ 1) Have a conversation with your users about how
the plugin should behave
2) Write it as a spec
3) Give it to us
”
#atlascamp @delitescere
31

32. Overheard
“ Consumer-Driven Contracts are some
crazy awesome!
jgraham@atlassian.com
”
#atlascamp @delitescere
32

33. ✴ Object Design book
http://www.amazon.com/Object-Design-Roles-Responsibilities-
Collaborations/dp/0201379430
✴ Domain Driven Design site
http://www.domaindrivendesign.org
✴ Using Mocks and Tests To Design Role-Based Objects article
http://static.mockobjects.com/files/usingmocksandtests.pdf
✴ Introducing BDD blog
http://dannorth.net/introducing-bdd/
✴ Consumer-Driven Contracts article
http://martinfowler.com/articles/consumerDrivenContracts.html and
http://iansrobinson.com/category/consumer-driven-contracts/
✴ Rest In Practice site
http://restinpractice.com/
33

34. Cheers, big ears
Josh Graham
SaaS Architect, Atlassian
jgraham@atlassian.com @delitescere