In Charge of Testing

As a Test Manager I oversee the testing in a project or program – I am usually the only testing specialist in the project, so, I need the right leadership skills and the right tools to succeed. I have to own the data about the testing and quality activities.

As the test manager I need to facilitate a quite a range of testing activities:

I need to balance that I need to know what’s going on (with regards to testing) but without micromanaging the people being involved in testing and quality activities. My role is to facilitate that testing things happen – like the project manager making project things happen. I cannot own the activities without owning the data about it. I need to cover the full spectrum of tests – from engineered (RDA and CI/CD) to people-based (scripts and exploration).

The most practical tool for a test manager with this scope is PractiTest, as there is more to testing than just the test cases [2]. The old term “ALM” [3] comes to mind – it is still relevant when I look for a full test management tool. I need to cover both the “inputs” to testing (requirements, tickets and user stories) and the “outputs” (bugs) in one location. I need the requirements and user stories in my tool, as I need to base my test analysis and planning on the delivery model (that may not always be agile). I need the bugs in the testing tool too, as bugs can happen in any work product of the project: documents, code base and even the tests. PractiTest acknowledge that there is more to IT projects than code.

I appreciate the key driver of PractiTest – that all activities happen in-flow. You don’t have to change window, stack pop-ups or go to another tool in order to run the tests or create bugs. Creating bugs happens in context of the test case and seamlessly moves all data about the run to the bug. Everything you need to do is context-based, and available to you on screen. And it has some cool features of read-only links to graphs for management reporting, and a smart built-in “rapid reporter” for exploratory testing notes.

It can be a challenge to switch to PractiTest if you are in a compliance setting, if you need on-Premise or if your team generally uses Azure DevOps (the tool formerly known as TFS). To get the full potential of Azure DevOps, though, you need the full Microsoft Test Pro licenses, so it’s not a free tool either – nor is DevOps intuitive for testing things doesn’t have the code available. As with Azure DevOps PractiTest is also SaaS only, with multiple data centers for regional data compliance. As there is always inertia towards a commodity it won’t be long before there is no good arguments to have test management tools on-Premise and for the tool vendors to provide the compliance certificates (ISO/SOC really should be sufficient, IMO).

Out of the box PractiTest supports the categories of testing above (engineered, scripted, exploratory) and has the necessary integrations too: Surefire for unit testing, Maven for CI/CD, Jira, ServiceNow or any other ITSM for requirement input. There is even a two way integration to Azue DevOps. As the web design is “responsive” it could probably run off a tablet. That would enable easier test documentation for field tests. It would be even better to have a small version of it on a phone and be able to use the camera for “screen shots”.

At work I am currently running a large project regarding customizing and implementing a standard commercial software system, PractiTest would fit right in, as we have the following test activities:

  • Unit test by the developers
  • Automation by test engineers
  • Exploratory test by Subject matter experts
  • Formal scripted testing with end users

And I need to own the data around all of this, if I want to in in charge of the testing (and not only the testers). We are very few software testing specialists on the project team, but as the manager of testing I need to cover many other people performing the testing. This transforms my role from test management to one about leadership, coaching, and facilitation of testing being performed by the SMEs – and anyone else really.

I will be talking about Leading When the Subject Matter Experts Test at ConTEST NYC 2019 until then read more about leadership:

  1. Anthropologists and similar humanities educations can be great BA’s
  2. looking at you Test Rail ūüėČ
  3. ALM = Application Life Cycle, like Micro Focus Quality Center etc.

Disclaimer: This is an influencer review sponsored by PractiTest.

Advertisements

Recruit for Curiosity

Recruiting for testing roles these days should be mostly about curiosity, problem-solving and less about productivity and text book knowledge. Recruit for right brain skills Рnot so much operational process jockeys. 

Recently at UKSTAR 2018 Simon Prior talked about his investigation into University programs and their rare courses in testing. This lead to his twitter discussion under the tag: #makeAtester where the top responses of skills required was curiosity. Quite in line with the State of Testing Survey 2017 that lists key communication skills as most looked for when hiring for testing roles. Both surveys establish that testers are knowledge works.

IMG_3614

Similarly HFresearch have compiled an analysis that even on a management level the trend is to hire for creative thinkers over “operational experts that improve business performance and productivity”.¬†¬†Talent focus should be on right brain thinkers over –¬†The wonks who spend all day staring at spreadsheets, focused on execution “left-brained” activities are less in demand .

But where do we find curiosity training?

If that is the skills we are looking for perhaps we should stop looking at university programs in computer science or engineering, when we want to recruit testers. I have a computer science master degree, and that was really theoretical and while it somewhat focused on problem solving, the lesson was rarely about thinking outside the box.

I think I would rather higher with business domain skills and train testing theory, than hire a process jockey with no experiences in besides textbook examples. That’s also how I came into testing myself, practical activities first – formal training later.

Perhaps it’s not as such important to have an university degree to get into testing. Though it helps ūüôā A diverse background is important, I know of librarians, laboratory technicians and humanities majors that bring good competencies to the testing field.

Finding one higher education that focuses on building curiosity, whole picture thinkers is hard – perhaps dungeons and dragons, as also discussed at the conference?

Shifting is more than Shift Left

Links on the topic: Shifting is more than Shift Left as presented at the OnlineTestConf Fall 2017.

My own writings:

by @KatjaBudnikov #katjasays
by @KatjaBudnikov #katjasays

Teaser for Online Test Conf 2017

I’m speaking at the Fall 2017 Online Test Conference on the topic: Shifting is more than Shift Left¬†

Change is happening to the testing activities. Shift-left automates and codifies the testing activities. Shift-right does it for production.

This session will be about a couple of other trends, changes and shifts that’s happening to testers and test managers.

‚Äď Shift-Coach, where It‚Äôs more about coaching teams.

‚Äď Shift-SME, where it‚Äôs more about business savvy.

‚Äď Shift-Deliver, where it‚Äôs more about the road to production

9

Blogposts:

Teaser for Experiences in Testing Infrastructure Projects

I’m presenting at UKSTAR 2018¬†on the Topic:¬†Experiences in Testing Infrastructure Projects.¬†The content is a continuation of my materials and talks about testing outside the SDLC, in this context operations and infrastructure. It‚Äôs additional problems and examples compared to ‚ÄúHow to test in IT Operations‚ÄĚ at Nordic Testing Days 2016.

UKSTAR 10% OFF ANY TICKET WITH CODE
UKSTAR 10% OFF ANY TICKET WITH CODE

Relevant blog posts, but not talk content:

The talk is in the same field as this talk – by Mike Talks @testsheepnz although with no applications on top… and other stories ūüėČ

 

Shift-Right, you wild one!

The Shift-Right label is that more and more testing (and checking) can happen on the live application in production. Some call it monitoring, some call it Testing in the Wild. It is a very wild idea for some people and some contexts #YMMV. It may very well be the best way of testing in some contexts.

Once I consulted on a network stabilization and delivery optimization project for a consumer bank. They had many issues in their production environment… I strongly advocated that they did test controlled and structured¬†in production on the network changes and other operational activities. (I have talked about¬†‚ÄúHow to Test in IT operations‚Äú at¬†Nordic Testing Days 2016). More on testing during IT deliveries in Shift-Deliver.

Shift-Right is trend that people have covered well before me, here are some pointers:

The key is really as Alan puts it “testers should try to learn more from the product in use” and with that comes the tools of Google Canary builds, NetFlix Chaos Monkeys¬†etc.

kabuum

This trend goes along with¬†Shift-Coach,¬†Shift-Left¬†and Shift-Deliver¬†discussed¬†separately.¬†Initially I considered shift-right to be¬†regarding consulting, but after hearing¬†Declan O’Riordan¬†at DSTB 2016¬†I realized that shift-right was the right label for test in production, testing in the wild etc.

Similar posts regarding things in the wild: Bugs Happens, The Kcal bug, Tradition is a choice and Can you see beyond the visible.

The Shift-Coach Testing Trend

Shift-Coach is when testers and test managers trends towards being coaches and facilitators of the testing activities. Shift-Coach is more about leading the testing than leading the testers to paraphrase from @DevToTest Joe DeMeyers blog post.

The ground breaker for this trend, is to me, the talk “How I Lost My Job As a Test Manager” presented at Test Bash 2015 by Stephen Janaway. Stephen explains how reorganization of the test manager role forced him to be more a facilitator than embedded in the teams.¬†Similarly many other great test managers talk more and more about people skills and coaching, especially in agile projects. I want to define shift-coach¬†around¬†the facilitation testing activities, and place testers that doubles as scrum masters in the Shift-Deliver¬†trend.

In traditional (v-model) projects testing has often included people that were not professional testers; Рin user acceptance tests this has often been business subject matter experts. The testing was done by someone with the best knowledge of the topic, and that may not have been the professional tester. That more and more projects do this Рmore and more, is a big challenge for many testing folks. But it is a significant trend in testing world of 2016.

Shift-Coach trend is visible when Alan Page  talks at Test Bash Philly 2016:

You’ve heard the rumors, and you’ve seen it happen. An organization or development team decides they don’t need testers, and you have big questions and massive concerns. Is quality not important anymore? Are they irresponsible or idiotic? Are their hats on too tight? Do testers still have jobs?

Alan Page is a career tester who has not only gone through the ‚Äúno-tester‚ÄĚ transition, he‚Äôs taking it head on and embracing it. Alan will share experiences, stories, strategies, and tactics (and failures) on how he‚Äôs taken everything he‚Äôs learned in over twenty years of software testing, and used those skills to have an impact on software engineering teams at Microsoft. Whether you‚Äôre going through this transition yourself, think it may be coming, or just want to tell someone what an absurd idea this is, this is the talk for you.

This trend goes along with Shift-Right, Shift-Left and Shift-Deliver discussed separately. I discussed these trend labels at Nordic Testing Days 2016 during the talk “How to Test in IT operations“ and coined the labels on the EuroStar Test Huddle forum.

legocoach
Drive the Testing – Coach!