Вы находитесь на странице: 1из 1

Re-thinking the Test Case Preparation

The previous role I held was QA Group Lead, in a product company. My responsibilities
implied constant aim for innovation and efficiency, considering the workflows and processes of
the QA engineers.
I needed to ensure that QA group's objectives are aligned and serve to met the company goals:
caring for customer satisfaction - through a qualitative product and a short time to market -
through frequent releases, with a short lead time. Given the above directions, I reviewed the actual
processes, identifying the waste and searching ways to remove it.
One of the time consuming steps within the feature testing process was the test case
preparation. Test cases design was performed using Test Lodge, a test case management tool. Test
cases were written as phrases (using the traditional way of defining the preconditions, steps to be
executed, expected results etc.), taking a lot more time than actually executing them. The tool
itself enabled this test description process and offered some reporting features, similar to other
tools available on the market, having also some disadvantages (e.g. searching functionality was
not retrieving proper results, repetitive steps needed to be performed). The activity itself was
rather demotivating for the QA engineers, not adding much value to testing, considering both
the time/ effort spent for test cases writing, but also the inefficiency to review the long list of
scenarios (by any team member). The limited time available for this testing phase was consumed
The need of changing the tool was evident, but the other similar options were not resolving
the waste itself. We needed to change the process, so the the test cases design

Вам также может понравиться