API tools faq
paste
Guest User

Untitled

a guest
Feb 28th, 2018
387
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 14.13 KB | None | 0 0
raw download clone embed print report
  1. .comment
  2. Comments in this file are this color and wrapped in a "div class="comment"". There not expected to be in the output
  3.  
  4. .run
  5. .info
  6. date command project etc.
  7. .summary
  8. %h3
  9. Summary
  10. %span (click on any summary item to go the step)
  11. %ul.steps
  12. %li.step.pass
  13. %a{ :href => "#f1c1s1" } .
  14. %li.step.pass
  15. %a{ :href => "#f1c1s2" } .
  16. %li.step.pending
  17. %a{ :href => "#f1c1s3" } p
  18. %li.step.fail
  19. %a{ :href => "#f1c1s4" } f
  20. .stats
  21. .scenario 1 scenario
  22. .pass 3 steps passed
  23. .fail 1 step failed
  24. .pending steps pending (2 with no step definition)
  25.  
  26. .controls
  27. %h3 Controls
  28. .comment
  29. These would use javascript to make the output below more navigable.
  30. %ul.collapse
  31. collapse
  32. %li
  33. %button{:type => 'button'}
  34. all
  35. %li
  36. %button{:type => 'button'}
  37. steps
  38. %li
  39. %button{:type => 'button'}
  40. scenarios
  41. %li
  42. %button{:type => 'button'}
  43. features
  44. %ul.expand
  45. expand
  46. %li
  47. %button{:type => 'button'}
  48. features
  49. %li
  50. %button{:type => 'button'}
  51. scenarios
  52. %li
  53. %button{:type => 'button'}
  54. steps
  55. %li
  56. %button{:type => 'button'}
  57. all
  58.  
  59. .comment
  60. should we just bookmark steps, or should we bookmark features and scenarios as well?
  61. %p currently bookmarking all using convention for name
  62. %ul
  63. %li f for feature
  64. %li c for scenario
  65. %li s for step
  66. %p so the first step in the second scenario of the first feature will have a name 'f1c2s1'
  67. .feature
  68. .bookmark
  69. %a{:name => 'f1'}
  70. .title Feature
  71. .description
  72. In order to keep order administration simple
  73. .br Customers
  74. .br Must confirm their order before payment
  75. .scenario
  76. .bookmark
  77. %a{:name => 'f1c1'}
  78. .title Basic Scenario
  79. %ul.steps
  80. %li.step.pass
  81. .bookmark
  82. %a{:name => 'f1c1s1'}
  83. .text
  84. Passing step Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
  85. .match
  86. path/to/matching/step/with/line/number xx
  87. %li.step.pass
  88. .bookmark
  89. %a{:name => 'f1c1s2'}
  90. .text
  91. Passing step Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
  92. .match
  93. path/to/matching/step/with/line/number xx
  94. %li.step.pending
  95. .bookmark
  96. %a{:name => 'f1c1s3'}
  97. .text
  98. Pending step Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
  99. .match
  100. path/to/pending/step/with/line/number xx
  101. %li.step.fail
  102. .bookmark
  103. %a{:name => 'f1c1s4'}
  104. .text
  105. Failing stepLorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
  106. .match
  107. path/to/failing/step/with/line/number xx
  108. .trace
  109. Trace LineLorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
  110. %li.step.skipped
  111. .text
  112. Skipped stepLorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
  113.  
  114.  
  115. .scenario
  116. .title Nested steps scenario
  117.  
  118. %ul.steps
  119. %li.step.pass
  120. .text
  121. Passing step implemented by calling other steps
  122. .match
  123. path/to/matching/step/with/line/number xx
  124. .nest
  125. path/to/nested/step/with/line/number xx
  126. .nest
  127. path/to/nested/step/with/line/number xx
  128. .nest
  129. path/to/nested/step/with/line/number xx
  130. .nest
  131. path/to/nested/step/with/line/number xx
  132.  
  133. %li.step.pending
  134. .text
  135. Step implemented by calling other steps where one step is pending
  136. .match
  137. path/to/matching/step/with/line/number xx
  138. .nest.pending
  139. path/to/line/calling/pending/step/with/line/number xx
  140. .nest.skipped
  141. path/to/skipped/nested/step/with/line/number xx
  142. .nest.skipped
  143. path/to/skipped/nested/step/with/line/number xx
  144. %li.step.fail
  145. .text
  146. Failure occuring in nested step
  147. .match
  148. path/to/matching/step/with/line/number xx
  149. .nest.fail
  150. path/to/line/calling/failing/step/with/line/number xx
  151. .nest.skipped
  152. path/to/skipped/nested/step/with/line/number xx
  153. .nest.skipped
  154. path/to/skipped/nested/step/with/line/number xx
  155. .trace
  156. Trace LineLorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
  157. %li.step.skipped
  158. .text
  159. Skipped step
  160.  
  161. .scenario
  162. .title Step tables scenario
  163.  
  164. %ul.steps
  165. %li.step.pass
  166. .text
  167. Passing step with table
  168. .table
  169. .comment
  170. Assumes cucumber converts tables into proper table html. If not would
  171. put table stuff in a %pre%code
  172. %table
  173. %tr
  174. %th name
  175. %th email
  176. %th phone
  177. %tr
  178. %td Aslak
  179. %td aslak@email.com
  180. %td 123
  181. %tr
  182. %td Joe
  183. %td joe@email.com
  184. %td 234
  185. %tr
  186. %td Bryan
  187. %td bryan@email.org
  188. %td 456
  189. .match
  190. path/to/matching/step/with/line/number xx
  191.  
  192. %li.step.pending
  193. .text
  194. Pending step with table
  195. .table
  196. %table
  197. %tr
  198. %th name
  199. %th email
  200. %th phone
  201. %tr
  202. %td Aslak
  203. %td aslak@email.com
  204. %td 123
  205. %tr
  206. %td Joe
  207. %td joe@email.com
  208. %td 234
  209. %tr
  210. %td Bryan
  211. %td bryan@email.org
  212. %td 456
  213. .match
  214. path/to/line/calling/pending/step/with/line/number xx
  215. %li.step.fail
  216. .text
  217. Failure in step with table
  218. .table
  219. %table
  220. %tr
  221. %th name
  222. %th email
  223. %th phone
  224. %tr
  225. %td Aslak
  226. %td aslak@email.com
  227. %td 123
  228. %tr
  229. %td Joe
  230. %td joe@email.com
  231. %td 234
  232. %tr
  233. %td Bryan
  234. %td bryan@email.org
  235. %td 456
  236. .match
  237. path/to/line/calling/failing/step/with/line/number xx
  238. .trace
  239. Trace LineLorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
  240. %li.step.skipped
  241. .text
  242. Skipped step
  243.  
  244.  
  245. .outline
  246. %h3 Outline
  247. .comment Going to use square brackets instead of angle brackets here.
  248. .comment
  249. Taking the approach that an outline is just a quick way of specifying many different scenarios, so as far as results are concerned I'm just going to show every one as a seperate scenario. Now if I want to get cute and reduce the output then I can
  250. %ul
  251. %li Use javascript to collapse the children
  252. %li Use javascript to examine the children and style the parent based on the presence of fail skipped and pending elements
  253.  
  254. %ul.steps
  255. %li.step Given there are [start] cucumbers
  256. %li.step When I eat [eat] cucumbers
  257. %li.step Then I should have [left] cucumbers
  258. .examples
  259. %table
  260. %tr
  261. %th start
  262. %th eat
  263. %th left
  264. %tr
  265. %td 12
  266. %td 5
  267. %td 7
  268. %tr
  269. %td 20
  270. %td 5
  271. %td 7
  272. .scenario
  273. %ul.steps
  274. %li.step.pass
  275. Given there are [12] cucumbers
  276. .match
  277. path/to/matching/step/with/line/number xx
  278. %li.step.pass
  279. When I eat [5] cucumbers
  280. .match
  281. path/to/matching/step/with/line/number xx
  282. %li.step.pass
  283. Then I should have [7] cucumbers
  284. .match
  285. path/to/matching/step/with/line/number xx
  286. .scenario
  287. %ul.steps
  288. %li.step.fail
  289. Given there are [20] cucumbers
  290. .match
  291. path/to/matching/step/with/line/number xx
  292. .trace
  293. to many cucumbers
  294. %li.step.skipped
  295. When I eat [5] cucumbers
  296. .match
  297. path/to/matching/step/with/line/number xx
  298. %li.step.skipped
  299. Then I should have [7] cucumbers
  300. .match
  301. path/to/matching/step/with/line/number xx
  302.  
  303. .feature
  304. .bookmark
  305. %a{:name => 'f2'}
  306. .title Feature with Background
  307. .description
  308. In order to keep order administration simple
  309. .br Customers
  310. .br Must confirm their order before payment
  311. .background
  312. %h3 Background
  313. .comment
  314. This section shows the background steps, but not the results of the background being run
  315. %ul.steps
  316. %li.step
  317. .text
  318. Background step
  319. .match
  320. path/to/matching/stepdef/with/line/number xx
  321. %li.step
  322. .text
  323. Background step
  324. .match
  325. path/to/matching/stepdef/with/line/number xx
  326.  
  327. .scenario
  328. .bookmark
  329. %a{:name => 'f2c1'}
  330. .title Basic Scenario
  331. .background
  332. %h3 Background
  333. .comment
  334. This section shows the background steps, actually being run. It is envisaged that this would be collapsed by default unless something went wrong.
  335. %ul.steps
  336. %li.step.pass
  337. .bookmark
  338. %a{:name => 'f2c1s1b1'}
  339. .text
  340. Background step
  341. .match
  342. path/to/matching/stepdef/with/line/number xx
  343. .comment
  344. background steps would show in the summary for each scenario, and would have their own bookmark
  345. %li.step.pass
  346. .bookmark
  347. %a{:name => 'f2c1s1b2'}
  348. .text
  349. Background step 2
  350. .match
  351. path/to/matching/stepdef/with/line/number xx
  352. .comment now we are back to the normal steps
  353. %ul.steps
  354. %li.step.pass
  355. .bookmark
  356. %a{:name => 'f1c1s1'}
  357. .text
  358. Passing step
  359. .match
  360. path/to/matching/step/with/line/number xx
  361. %li.step.pass
  362. .bookmark
  363. %a{:name => 'f1c1s2'}
  364. .text
  365. Passing step
  366. .match
  367. path/to/matching/step/with/line/number xx
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!