Test Planning in 2021 Part 3: Testing in the Real World - TestRail

Test Planning in the Real World

On-Demand Panelist Webinar

Watch the full replay above, or catch the highlights by reading below.

 

Meet the Panelists

  1. Srilata Meka – Senior Salesforce QA Analyst at UKG
  2. Robin Fey – Software Quality Manager at Nexible
  3. Pablo Maurin – Director of Quality Assurance at Cardinal Peak

Each panelist answered questions asked by the moderator, TestRail Product Marketing Manager Matthew Caponigro.

Question: How do you plan your testing?

Srilata: We divide our testing into new functionality and regression testing. Our new functionality testing has a template document for our planning phase. This is when requirements are gathered and many meetings are held. Once planning is complete, the test cases are then written out in TestRail and ready for testing! And last but not least, the regression testing process involves updating the regression test suite, removing unwanted test cases, and setting up automation scripts to run smoothly in the Salesforce preview sandbox environment.

Robin: I play a consulting role within our testing to make sure there are no roadblocks within any testing processes. Every other week, the team presents the new or revised test plan and this is when I offer feedback on how to structure each test case, mainly in test automation.

Pablo: We take a light and dynamic approach because every one of the products that we are testing is different. There is always a well-defined delivery date for the product, so we must always plan enough time to test so that we are confident when the product is ready to be delivered or manufactured.

Question: What is one mistake that you’ve made around test planning?

Pablo: “It’s never one and done.” Never assume that when you have a test plan that it will run smoothly. You’re halfway through testing, you discover certain bugs, customer priorities, and even timelines change. So you have to update your test plan to decide how to address it.

Robin: In the beginning, I wanted to deliver everything on my own. If I had asked for feedback early in the testing process, I would have saved a lot of my time and effort.

Srilata: Not being specific with test planning. Leaving out criteria such as low, medium, or high priority for a certain feature or bug is one to name a few. Including the level complexity of the project to the QA LOE (Level of Effort).

Question: What advice would you give yourself earlier in your career?

Srilata:

1. Adopt the Shift Left approach, which emphasizes testing earlier and often.

2. Put into practice the Three Amigos. Business, development, and testing. People holding these different perspectives should collaborate to define what to do, and agree on “what is done”

3. Do not forget regression testing after defect identification or before user acceptance testing. NEVER FORGET IT.

Robin: Communication and transparency are key. 

Pablo: Remember why you’re doing this. At the end of the day, you’re testing for the end-user. Don’t over compartmentalize, it’s the end-user that matters most.