JBOSS 커뮤니티의 Integration test Tool 소개

1. 테스트

2. 어디까지

3. 해봤니?
arquillian을

4. 이용한

5. Real

6. Objects

7. 테스트
전성욱

8. (allnewangel@gmail.com)

10. Who

11. am

12. I
l SAP

13. hybris

14. 컨설턴트

15.
l RHQ

16. UI

17. 한글화

18. -

19. Contributor
2

20. 3
No tests ➡️ ➡️ #fail

21. Unit

22. vs

23. Integration

24. Tests
l Unit

25.
– Fine-grained

26.
– Simple

27.
– Single

28. API

29. Call

30.
– Fast,

31. fast,

32. fast

33.
– Easily

34. run

35. in

36. an

37. IDE
4
l Integration

38.
– Coarse-grained

39.
– Complex

40.
– Component

41. interactions

42.
– Sloooooooooow

43.
– Run

44. in

45. an

46. IDE?

47. How?

48. 5

49. What if integration testing could be...?
l as

50. easy

51. as

52. writing

53. a

54. unit

55. test

56.
l run

57. in

58. the

59. IDE

60. (incremental

61. builds,

62. debugging,

63. etc)

64.
l ramped

65. up

66. in

67. phases

68.
l portable
6

69. Component models make life easier
7
l Component

70.
– Follows

71. standard

72. programming

73. model

74.
– Encapsulates

75. business

76. logic

77.
– Packaged

78. in

79. deployable

80. archive

81.
l Container

82.
– Host

83. process

84. for

85. deployed

86. applications

87.
– Provides

88. services

89. and

90. a

91. runtime

92. for

93. components

94.
– Gives

95. you

96. powerful

97. mechanisms

98. for

99. free

100. What

101. is

102. Arquillian?
8

103. A component model for your tests

104. 10

105. Arquillian

106. architecture
11

107. ShrinkWrap
12

108. Benefits

109. of

110. ShrinkWrap
l Incremental

111. IDE

112. compilation

113.
– Save

114. and

115. re-run

116.
– Skip

117. the

118. build!

119.
l Simple,

120. fluent

121. API

122.
l Container

123. deployment

124. adapters

125.
l Micro

126. deployments

127.
l Export

128. and

129. debugging
13

130. Fluent

131. archive

132. creation
14

133. Test

134. Runners
15

135. Containers
l remote

136. container

137.
l embedded

138. container

139.
l managed

140. container

141.
l https://docs.jboss.org/author/display/ARQ/Container
+adapters
16

142. Arquillian
17

143. Example

144. component
19

145. Unit

146. test

147. class
20

148. Arquillian

149. test

150. class
21

151. 22

152. How

153. does

154. this

155. all

156. works?

157. Setup
Maven,

158. Gradle,

159. Ant(+Ivy)

160. 25

161. 26

162. 27

163. 28

164. 29

165. 30

166. 31

167. 32

168. 33

169. 34

170. An in-container approach to integration testing
l Start

171. or

172. connect

173. to

174. a

175. container

176.
l Package

177. and

178. deploy

179. test

180. case

181. to

182. container

183.
l Run

184. test

185. in-container

186.
l Capture

187. and

188. report

189. results

190.
l Undeploy

191. test

192. archive
35

193. Demo

194. Pros

195. and

196. Cons
l Pros

197.
– Flexible

198.
– Portable

199.
– Opensource

200.
– Handy

201. even

202. for

203. tests

204.
l Cons

205.
– Maven

206. hell

207.
– one

208. test

209. class

210. per

211. @Deployment

212.
– too

213. much

214. capableties

215. —―

216. bit

217. large

218. learning

219. curve
37

220. Q

222. A

223. 감사합니다

224. JBoss

225. Community

226. (http://www.jboss.org)

227.
Korea

228. JBoss

229. User

230. Group

231. Facebook

233.
(https://www.facebook.com/groups/jbossusergroup/)
40