The evolution which came with the Arquillian, award-winning integration test framework, and Selenium, outstanding tool for UI automation, allows to write high-quality tests. But these technologies can’t save the world by themselves, since they are leaving too many questions open: * Does Selenium cover everything? It covers page transitions, a simple JavaScript interaction and a portion of DOM. Is it really enough? * Mocking requests for testing server-side code is pain. Is it necessary? * Are you able to detect that your component’s visual representation changes? * Does investigating these changes involve a disproportionate amount of effort? * Isn’t manual test development too expensive? What if you could fill all the above gaps?

1. Designing Top-Class Test Suites
FOR WEB APPLICATIONS
Lukas Fryc

2. $ whoami
Lukas Fryc
@LFryc
JBoss Software Engineer
Arquillian Commiter

3. Agenda
● Agility in Testing
● Testing: Basics & Principles
● Client-Side Testing
● Unit Testing
● UI Automation
● Foundations of Real Tests
● JSFUnit.NG
● Speeding up Development
● JRebel extension

4. Testing
Testing
Testing
Testing #Agile
Testing
Testing
#TDD Testing
Testing
Testing
Testing “You can hear about testing
Testing from everywhere!”

5. “How would you complete
equation?
What word do you
imagine when someone
says testing?”
Testing = ?

6. Testing = Pain

7. “What about changing
that equation a little bit?”
Testing = Enjoyable!

8. “But testing of large
enterprise application can
hardly can be enjoyable.”
Enterprise Java Web Application
“You need to write all the
test harness at own and
study all the tools.”

9. Reinventing the Wheel

10. No one saves the World?

11. “There is one: his name is
Ike. He comes from far,
deep space from planet
Arquillian...”

12. “Ike brings heavy gear for
fighting with alien
bugs...”

13. “...and he is proud to
share his powerful gear
with us!”

14. “At first, he comes with
Ability to split one big
deployment into many
small - testing as little as
components as possible
in separation.”

15. “And he makes sure
these deployments work
on various of Earth's
application servers.”

16. “...and once he deploys
the deployment into
container, he makes sure
you have all the goodness
from inside available
using dependency
injection.”

17. “...and that all backed
with strong development
tools.”

18. “You can run it just from
your IDE, re-using what
you already know.”
JUnit TestNG

19. Testing Revolution

20. Ike brings tests to the Server

21. But what about the Client?

22. The little bit of Theory...

27. “Let's have ideal testing
pyramid in mind,
otherwise...”

28. Enough Theory!

29. Let's bring tests to the Client

30. JUnit
TestNG

31. “But it isn't as simple as
in Java - many different
environments.”

32. “Fortunately there is tool
which allows you to write
tests in unified API for all
those browsers.”

33. “And the even supports
mocked browsers with
same API.”

34. W3C: Browser Automation Spec

35. Oh, such a great tool!

36. Let's invade client!

37. “Ouch, we need some
abstraction!”

38. “Even if we use favorite
programming language,
we can end up with many
tests which take days to
pass and may quickly
turn out into maintenance
burden!” Java
C#
Python
Ruby
PHP
Perl

39. At least, the app is covered...

40. “But this is what actually
Selenium see.”

41. Black Box

42. “Selenium is able to test
transitions between
pages.”
State Transitions

43. “...and a portion of all the
page source code –
JavaScript handlers,
selected CSS and DOM
changes as reaction to
user interaction.”
A little bit of...
DOM / JavaScript / CSS

44. Let's change the game...

45. Right tool for the Job

46. “Let's take an
outstanding UI
automation tool...”

47. “and add your favorite
language.”

48. “and little bit of Alien
technology.”

49. Arquillian Drone
Ike's Hard-Worker

51. “Drone comes to bring
the browser to your test.”

52. Help Devs get along with QA
Developers focused on tests
QA focused on automation
arquillian.xml configuration for cross-browser testing

53. Let Ike invade the Client

54. “But something else is
needed to make your
tests green.”

55. “Something enough
strong to handle all the
inconsistencies.”

56. “Let's deploy that to the
browser page and see
what happens!”

57. Arquillian Graphene
Shielding Ike from Maintenance Burden

58. Strongly type-safe
Proven to handle AJAX
Request Guards
jQuery Selectors

59. guardXhr(button).click();
guardHttp(button).click();

60. Strongly type-safe
Proven to handle AJAX
Request Guards
jQuery Selectors
Page Extensions – Script Injection
Cross-cutting concerns
Interceptors

61. @JavaScript(“document”)
public interface Document() {
String getTitle();
}
@Inject
Document document;
// calls 'return document.title;'
document.getTitle();

62. Isn't that too low-level?

63. “Let's look for something
on higher level.”
Reusable Abstractions

64. “Introducing well-known
Selenium pattern:”
Page Objects

65. “Imagine you have
page with all the
elements and you
express them as
fields in the class.”

66. “Page Objects allows
you to abstract page-
oriented logic into
objects.”

68. “But for modern AJAX-
based application, it's
simply not enough.”

69. “In enterprise
applications, you use
UI components that
encapsulates low-
level logic.”

70. “We could create the
model of these
components from
their user's point of
view?”

71. @FindBy(id=”form:calendar”)
Calendar calendar;
calendar.setDate(new Date());

72. @Component
public class Calendar {
@Root
WebElement driver;
@FindBy(css=”.dateButton”)
WebElement button;
public void setDate() {
input.click();
}
}

73. Component Objects
Will be part of Arquillian Graphene 2.x

74. “When each
framework and library
providing UI
components will
design component
objects the same as it
share their code, it
will be testing much
more simpler.”
Call to Action:
Write & Share Component Objects

75. Let's do the review...

76. “Now, we can simply
write tests on proper
level of abstraction
with minimum
efforts.”

77. 3 Missing
Pieces

78. “What is missing here?
No manual coverage and
no unit and integration
tests for client-side!”
JUnit
TestNG

79. How to avoid manual testing?

80. “We can automatically
snap screen-shots of the
whole pages and
compare them with
historical data – it's
proven that rendering on
one particular browser
and platform, images will
be binary same.”
Screen-shot Comparison

81. Automated Visual Verification

82. The Music of the Future?

83. Arquillian RushEye
Google Summer of Code 2012

84. “Server is already
covered with unit and
integration tests, but
what about the same
goodness for client?”
JUnit
TestNG

85. “Unit testing of client
is even more
important than unit
testing of server,
since it suffers from
environment
diversity.”
Unit Testing Client

86. Unit Testing Frameworks
QUnit, Jasmine, JsMockito
Test Runners
JSTD, Selenium, Maven

87. “But once those unit
tests are written, how
to automate them?
Without automation,
they are not tests.”
Yet another tool to configure?

88. Reuse the Automation Setup

89. “For writing actual
tests, you can use
your favorite JS client
testing tool.
We are actually
working on
integration with
QUnit.”
Arquillian
Drone + QUnit | JSTD
Maven / Jenkins / IDE

90. “JavaScript testing does not
scale!”
~John Resig
http://ejohn.org/blog/javascript-testing-does-not-scale/

91. TestSwarm
Crowd-sourcing for Browser Coverage
Jenkins integration
“But it is rather for
open source projects,
right?”

92. “For corporates, it is
more suitable to use
cloud services:”
Browser Tests in the Cloud
SauceLabs On Demand
Integration with Arquillian comming

93. “And once the client is
covered too, only
integration tests for client
are missing.”
JUnit
TestNG

94. “The integration
testing of client is
actually making sure
it communicates with
server as expected.”
Client + Server Integration

95. “We have browser and
test on one side and
server on opposite side.”

96. “With UI automation, we
are sending request from
client to the server.”

97. “And server generates
response.”

98. Black Box

99. “On the other hand, when
we are testing server
from its JVM, we are
mocking requests, which
invokes verification
code.”

100. Don't mock me

101. The Tour to the Server
There and Back Again

102. “Let's make the
connection between client
and server live.”

103. “Once the requests goes
to the server, the test
code is serialized and
sent as part of the
request.”

104. “Server de-serializes the
testing code from request
and uses it for verification
of the server state in
several lifecycle phases.”

105. “Offering all the gear
which Arquillian offers,
including test enrichment
for injection of test
dependencies.”

106. “Then the testing object
is serialized again and
sent back to the client,
which can validate it.”

107. “Client can verify the
response and send
subsequent request.”

108. Crazy idea?

109. “But it is already
possible!”
JSFUnit

110. JSFUnit
HtmlUnit
Asserts end of the Request State
JSF only
JSFUnit .NG (next generation)
Selenium / any other HTTP client
Lifecycle
Any injectable resource
Any Servlet based framework

111. “Now, we are covered!”
JUnit
TestNG

112. Client Invasion

113. That's it...

114. No, It can't be without....

115. Mobile

117. “Drone can instantiate
browser emulator or
connect to real device.”

119. “And create the browser
within the
emulator/device.”

120. Arquillian Android
Emulating Mobile Platform

122. Development on Steroids

123. Speeding up Development
Reusable Browser Session
Arquillian JRebel Extension

124. Arquillian

125. Experience the Future Now

126. I must know more...

127. http://bit.ly/arq-preview

128. http://bit.ly/arq-users

129. Getting Involved

130. http://github.com/arquillian

131. http://bit.ly/arq-devs

132. http://bit.ly/jboss-testing

133. #jbosstesting @ irc.freenode.net

134. #Arquillian

135. Enjoy the Testing!

136. Questions for Ike?
@LFryc
http://bit.ly/arq-blog
http://bit.ly/lfryc

137. Some photographs and pictures used in this
presentation are authored by various authors
and released under the Creative Commons
license
http://www.flickr.com/photos/nickrussill/150410613/
http://www.flickr.com/photos/audreyjm529/1240909256/
http://www.flickr.com/photos/jo-h/6200225665/
http://www.flickr.com/photos/stevendepolo/3796415185/
http://watirmelon.com/2012/01/31/introducing-the-software-
testing-ice-cream-cone/