Timeline for Style of acceptance test cases? (BDD)
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 29, 2015 at 1:00 | comment | added | Ethel Evans | We use Git, and actually keep the test cases in a Maven module with the service code (we share common test code via a test library, as we have multiple services and don't want to duplicate test code). The test cases are written in Java or Groovy. If we have manual Gherkins (G/W/T's), we just tag them as \@manual and \@ignore, then keep them in the same feature file as the automated Gherkins. We use Cucumber JVM to automate our Cucumbers. | |
| Oct 28, 2015 at 13:56 | comment | added | Mercfh | out of curiosity, where do you store your test cases? (what application i mean). | |
| Oct 26, 2015 at 2:32 | comment | added | Mercfh | I actually just ordered that book but haven't gotten the chance to flip through it. Thanks! | |
| Oct 23, 2015 at 21:18 | comment | added | Ethel Evans | Yes, absolutely. 3 to 7 lines long, usually. An excellent book for writing great G/W/T tests, BTW, is "The Cucumber Book" - links to both the default (in Ruby) and a newer Java version are at the bottom of this page: cucumber.io It's a very easy read, and covers both writing the G/W/T (aka Gherkins) and implementing the test steps using Cucumber. I hand it to everyone in the office who is getting started with BDD. | |
| Oct 23, 2015 at 15:18 | vote | accept | Mercfh | ||
| Oct 23, 2015 at 15:17 | comment | added | Mercfh | Sorry one more thing: Do you find when you do G/W/T test cases off user stories they are...short? They just don't seem very long. I mean user stories in general shouldn't be superlong regardless. (im still new to the whole BDD thing haah) | |
| Oct 22, 2015 at 19:52 | comment | added | Ethel Evans | For me, I usually do that and then just throw an "additional test notes" section under it. It's very casual, and scales well to the free time available. I will sometimes call out certain tests as "as time allows", if they are lower priority. ETA: Also, I do this in the JIRA / ticket itself. Not even a separate test plan. And, I think using the G/W/T as you are is perfect. | |
| Oct 22, 2015 at 18:35 | comment | added | Mercfh | Were just now really starting the "Scrum"/Agile process. So i've just been using the Given/When/Then tests for acceptance test cases based off user stories. Not sure if thats a good idea however. But since im a single QA in this company doing all different kinds of test plans seems like impossible work as a single person. | |
| Oct 21, 2015 at 20:50 | history | answered | Ethel Evans | CC BY-SA 3.0 |