Reputation
3,387
Next privilege 3,500 Rep.
Protect questions
Badges
1 8 38
Newest
 Custodian
Impact
~170k people reached

Nov
25
comment Exception Handling when accessing sub menu
implicit wait ++
Nov
25
comment Exception Handling when accessing sub menu
Catching exceptions in tests is often bad practice. This often results in the test failing further away from the actual issue, which makes tracking the root cause difficult. Generally, the test should fail as fast as possible, so the tester doesn't have to read the logs to figure out why the assert one or more functions later failed; it should fail right here.
Nov
25
comment How best to start making a suite of broken tests relevant again?
This is what worked for us. Better two or three key cases that are stable than lots of coverage that the devs ignore.
Oct
29
comment Style of acceptance test cases? (BDD)
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
23
reviewed Leave Open Performance requirements for web application
Oct
23
comment Performance requirements for web application
Voting to leave open, as QA professionals are often asked to come up with performance requirements, especially in small offices or startups. Reporting on performance is often a significant part of a QA professional's job in these situations.
Oct
23
reviewed Leave Open Downloading a file using Selenium Webdriver C# not working
Oct
23
reviewed Approve web tag wiki
Oct
23
reviewed Approve hardware tag wiki excerpt
Oct
23
comment Style of acceptance test cases? (BDD)
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
22
comment Style of acceptance test cases? (BDD)
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
21
answered Manually testing CMS components (blocks) layout permutations and variations?
Oct
21
reviewed Leave Open Correct CSS selector for selenium
Oct
21
answered Style of acceptance test cases? (BDD)
Sep
17
awarded  Custodian
Sep
17
reviewed Reviewed How to ensure Quality of the product with test cases?
Sep
17
reviewed Reviewed What is the best way to revert changes to test cases in MTM/TFS?
Sep
6
awarded  Custodian
Sep
6
reviewed Approve How to run TESTNG failed test cases in jenkins for maven project?
Sep
6
reviewed Close how to read and write file on mac system using java?