Timeline for Error-testing be with cucumber/capybaraweb
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 22, 2016 at 2:42 | history | edited | Phrancis |
edited tags
|
|
| Apr 4, 2016 at 10:47 | answer | added | Kyle Fairns | timeline score: 2 | |
| Apr 3, 2016 at 15:09 | vote | accept | user2367593 | ||
| Apr 3, 2016 at 2:19 | history | edited | 200_success | CC BY-SA 3.0 |
edited tags; edited title
|
| Apr 3, 2016 at 1:21 | answer | added | sled | timeline score: 7 | |
| Apr 3, 2016 at 1:11 | comment | added | user34073 | Cool. I thought it might not be pseudocode, but I don't know Cucumber, so I thought I'd better ask. Good question. | |
| Apr 3, 2016 at 0:41 | history | edited | Jamal | CC BY-SA 3.0 |
added 39 characters in body; edited title
|
| Apr 3, 2016 at 0:35 | comment | added | user2367593 | @Hosch250 This is actual code that tests a rails application. The given/when/then/and lines tell cucumber what to do (They correspond to ruby code in another file, but I was wondering what was the best way to write the cucumber steps and scenarios would be in the feature file.) The current way I have works (it is the second example in the question), but was wondering if it was implemented correctly (so I think it falls under "Best practices and design pattern usage"). | |
| Apr 3, 2016 at 0:35 | comment | added | Phrancis | I have retracted my vote to close after looking at Cucumber website, I did not realize at first that this was actual code. | |
| S Apr 3, 2016 at 0:27 | history | suggested | jacwah |
Add comparative-review
|
|
| Apr 3, 2016 at 0:26 | review | Close votes | |||
| Apr 3, 2016 at 8:04 | |||||
| Apr 3, 2016 at 0:15 | review | Suggested edits | |||
| S Apr 3, 2016 at 0:27 | |||||
| Apr 3, 2016 at 0:06 | review | First posts | |||
| Apr 3, 2016 at 0:14 | |||||
| Apr 3, 2016 at 0:05 | history | asked | user2367593 | CC BY-SA 3.0 |