791 reputation
510
bio website technologyandleadership.com
location California
age
visits member for 3 years, 5 months
seen Dec 17 '13 at 22:19

I have 3 years experience in test automation at PayPal and 2 yrs of programming experience. I am interested in tech talks and writing. I write insightful testing articles at www.technologyandleadership.com


Sep
24
awarded  Autobiographer
May
20
awarded  Yearling
Feb
8
awarded  Notable Question
Dec
30
awarded  Taxonomist
May
20
awarded  Yearling
May
6
revised Can someone offer suggestions for client based cross browser testing tools
Provided more details
Apr
1
answered Running tests in parallel using Jenkins Grid plugin
Mar
31
asked TestNG - how to share same browser session between two methods?
Sep
5
comment Building “slow to break” regression tests
+1 Hiding incidental details is a great point. It hides the complexity of the test case making it easy-to-read and to the point.
Jul
27
awarded  Popular Question
May
20
awarded  Yearling
Mar
17
comment What is customer focus testing and how do I implement it?
+1 This is a great answer! You need to put yourself in the shoes of the customer to do Customer Focused Testing. It is beyond just verifying what's given in the spec.
Mar
13
comment Tracking manual test cases which are automated
How do you pass on this information to the new testers joining the team? Do we need to pass the excel sheet/path to excel sheet each time? When you move to another project and a new resource joins the team this approach could cause issues
Mar
7
comment Tracking manual test cases which are automated
Excellent Idea Bj! We could develop a tool that automatically searches and reads the "tags" and exports that to a excel document for tracking
Mar
6
comment What should be the critieria for the selection of new feature test cases to be moved into build acceptance test suite?
I partially agree with that. After the test cases are moved to BAT the ownership does change. But before that, the new feature test cases author should be accountable for handover of a robust high quality suite to the BAT team. For the future releases the BAT team could be held accountable
Mar
4
comment What should be the critieria for the selection of new feature test cases to be moved into build acceptance test suite?
+1 These are very important points. Typically ownership of failures is a challenge because the resource who automated the new feature test cases might have moved to a different project when we are planning to move his test cases to BAT. The communication plan for failures, ownership and maintaining a high test code qualtiy are great points and deserves very high marks from me!
Feb
26
accepted What should be the critieria for the selection of new feature test cases to be moved into build acceptance test suite?
Feb
24
comment What should be the critieria for the selection of new feature test cases to be moved into build acceptance test suite?
+1 For emphasis on short feedback cycle which is very important
Feb
24
comment What should be the critieria for the selection of new feature test cases to be moved into build acceptance test suite?
+1 This is a great answer! We have build acceptance test suite in our organization to test whether the buid is ready for testing. We are also planning to give this suite to the DEV for testing before they deliver any bug fixes to ensure their fix does not break existing functionality. So I think, negative use cases are not good candidates for BAT. Is that correct?
Feb
24
asked What should be the critieria for the selection of new feature test cases to be moved into build acceptance test suite?