Scroll to top
en pl

2 DevOps assumptions that might make your test management process work better – respond of the TestFLO solution

Boguslaw Osuch - 10 February 2017 - 0 comments

DevOps in shortly is an attempt to connect different groups of professional teams. Crucial in this approach is trying to make the whole work faster with efficient communication at all levels, which is difficult in most of cases – but needs to be chased ‘cause that’s the only way to acquire market competitiveness nowadays.

In this article, I try to answer the question: How can it be possible to run DevOps spirit – based on speeding communication processes – in Test Management process with the use of TestFLO?

Main assumptions of DevOps that might be useful in Test Management process:

Proper communication and monitoring is crucial

  • In Test Management process we can define three main roles : Managers (understood as business representatives), Test Seniors (members of the team responsible for coordinating the whole test process), and Test Specialists (those who are responsible for manual and automat tests execution). To make the whole process efficient there is a need to run communication process used: clearly, automatically, and effortlessly for all the persons involved. Moreover, as a must, each member of the whole test process needs to be able to get to know at what level is currently run.The knowledge about coverage of specific test cases in relation to requirements is critical especially for managers. Summing up – it is not easy work.

Do whatever you can so as not to flip single tasks between teams

  • During daily routine there is a temptation to run separated tests and assign them to specific Test Specialists, Which could make the first impression of well and fast done work at the beginning, but it will not succeed in the long term. In every structure where one team flips tasks to the other and forgets about them, there is no chance for simultaneous communication and time-effective work. The best results are achieved when professionals can cooperate at all stages, and repeatable work is being defined upfront in specific templates.

How did we cope with previously presented assumptions and problems that might appear in respond of them?

Proper communication and monitoring is crucial

  • In TestFLO we gave the chance to monitor and assign issues at all levels.
    • At the beginning of the work with requirements analysts (testers or other business representatives) create specific Test Case Templates to make the whole process more easily repeatable and traceable.
    • Thanks to defined panel every person involved in test process can gain the knowledge about the coverage of specific Test Cases with given requirements.
    • Every Test Plan coordinator can see what kind of Test Cases fulfill them, and what kind of Test Steps the specific Test Case has passed or failed.

The columns that provide information of specific category are fully configurable. For example in every Test Case field can be added that will categorise for which web browser the test case was designed, and it will be shown in here.

TestFLO is giving you a chance not only quickly create Test Plans using Test Case Templates, but you can also  assign additional Test Case or Test Plan for Requirement at every stage of your work, commonly used when some new surprising test case appears, of course it is all seen at the dashboard.

Do whatever you can so as not to flip single tasks between teams

  • In the first step we have put an effort to force every person working on the planning stage to create Test Case Templates. It does not add almost any extra work at the very beginning, because you can create Test Plan from them within a few minutes. However, it allows you to have a repository of Test Cases that can be used every time in the future. So, if you are responsible for managing a testing process, you will just do it that way, and if you finish you just have to add specific Test Case Template (TCT) into Test Plan (TP). This solution allows you to run a regression test without any additional work, and what is more important, you will not flip single tasks between you, your team and developers.
  • Furthermore, communication between Testers (left column of the pic), with Developers (right) takes place in the real time. The Developer has a chance to receive information about all the defects (bugs) and solve them on the spot.

Key takeaways

  • To increase efficiency of your testing process be aware of two factors (taken from DevOps approach):
    • Proper communication and monitoring is crucial
    • Do whatever you can so as not to flip single tasks between teams
  • One of the ways to make them more efficient is to use:
    • TestFLO monitoring panel (added to each requirement)
    • TestFLO Process, that separates planning stage from execution (where particular instances of Test Cases are created on spot), and organised communication between Testers and Developers.

Try it for 30 days for free or schedule a demo with me.

PS to launch TestFLO Jira is needed – I can take care of that too, please just don’t hesitate to contact us.

Related posts