Migrate Idea

Of course (of course!) we were delighted to be asked to provide test support for an internal project which was upgrading an important and widely-used application and rationalising the data associated with it. Of course (of course!) the many application instances are intended to be standardised but, despite best efforts to be consistent, over time we've built up a load of special cases, workarounds, emergency patches and so on, all of which make this kind of migration task more difficult.

Of course (of course!) the deadline was both close and ambitious but there was enough time for us start to write automation to obtain a client-side view of the data and configuration on each instance (via an API) to provide an initial audit and then agree policy for migration with the various stakeholders based on that. We then extended the test code to generate an expectation of the equivalent client-side view for each server on its migrated instance which we'd check (via equivalent API) in the new software.

Of course (of course!) the migration policy turned out to be incomplete and ambiguous in places once the physical migration attempt began and we encountered discrepancies in the observed data, found that some of the data wasn't what we thought it was, identified errors in the migration, identified errors in the test code, were forced to modify policy, were forced to modify expectations, were forced to rework parts of the migration and so on as we went along.

Of course (of course!) across several rounds of implement-test-analyse-fix we converged on a stable system, the automation giving a broad brush regression test at a scale and speed impossible in manual testing but backed up by a team of testers interacting with the application. By the final iteration the automation wasn't in step with the implementation, but we were confident we knew where the major exceptions were and had plans to fix them.

Of course (of course!) we met the deadline and of course (of course!) there was no more test budget because the next priority was immediately upon us. But, of course (of course!) we weren't happy to accept that because the updated software hadn't failed at the point of switchover it would be just dandy once in production. So we looked for a cheap way to get some kind of quick stability test.

Of course (of course!) without budget our options were limited, so we decided to try recycling the test automation by leaving it running on a loop against each of the servers for several days. We had each experiment log to a unique file and write a pass percentage into it. At any given time we could simply grep the logs, import into Excel, and plot the pass rates for each instance of the application for each test set over time.

Of course (of course!) we knew that pass rates wouldn't be 100% in many cases because we never got back to fixing up the expectations of some of the checks. But in this round what we were interested in was the deltas: without some external action, the results should not change. If the results don't change, we have some evidence that the system is stable. When results did change, we investigated, but didn't attempt to change the test code's expectations. Instead we simply looked for further changes to the new pass rate.

In this chart, time point 4 looks like a transient infrastructure issue since all servers experienced a change in behaviour at the same time and then recovered. Server C's data disappeared at 6 suggesting that the test code might have failed in one iteration, but we don't know why without looking. The same server experienced a sharp delta at 9 while none of the other servers were affected, so probably an issue on that server to investigate. Server A changed behaviour at 7 and stayed there: perhaps a genuine data change, or perhaps some persistent failure.

Of course (of course!) there were some positive results: we identified one back-end server which had to be recommissioned due to disk problems and another which was not being load-balanced correctly. And of course (of course!) there was some noise and some false results which, if nothing else, on investigation confirmed that the system was working as expected. For instance, we found that contention for licenses prevented some suites from running occasionally. And then of course (of course) there was the growing confidence that constant usage wasn't of itself a problem for the new installations.

Of course (of course!) we did have to expend some resource on this work, but the analysis wasn't particularly onerous and we think the benefits were worth the cost. We tweaked things based on the early round of test to reduce the noise, identify patterns which could be safely ignored and so on. We also started to parallelise the same set of tests and so put more background load on the system as we became happier with the way it was functioning.

Of course (of course!) this kind of approach won't work everywhere and depends on some conditions being met, for example that changes in the data and configuration being checked are uncommon across the test period. It should be noted that it may also not expose different issues, or combinations of issues, that happen to have the same pass rate. Investigation of issues will probably be made more efficient if logging includes diagnostic information and time-stamps so that it can match up with server-side data when there's a need for finer granularity than the simple pass rates and, in fact, we found that grepping (although I'm using ack more these days) this richer data was a good way to perform quick investigations and look for patterns across servers not shown up by the basic pass rate.

Despite the caveats the method worked well on this project, and I'd use it again when I thought it would provide benefit. The implementation team liked it and thought we did a job of the highest quality, were the best testers they'd ever worked with, had great rapport with them, great team spirit, good fashion sense, great hair and smelt nice. OK, they didn't actually say that but they were thinking it, of course. (Of course!)

Image: http://flic.kr/p/4Jrzjx

Comments

Meet Me Halfway?

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "Stop answering my questions with questions." Sure, I can do that. In return, please stop asking me questions so open to interpretation that any answ...

Can Code, Can't Code, Is Useful

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "If testers can’t code, they’re of no use to us" My first reaction is to wonder what you expect from your testers. I am immediately interested ...

The Best Programmer Dan Knows

I was pairing with my friend Vernon at work last week, on a tool I've been developing. He was smiling broadly as I talked him through what I'd done because we've been here before. The tool facilitates a task that's time-consuming, inefficient, error-prone, tiresome, and important to get right. Vern knows that those kinds of factors trigger me to change or build something, and that's why he was struggling not to laugh out loud. He held himself together and asked a bunch of sensible questions about the need, the desired outcome, and the approach I'd taken. Then he mentioned a talk by Daniel Terhorst-North, called The Best Programmer I Know, and said that much of it paralleled what he sees me doing. It was my turn to laugh then, because I am not a good programmer, and I thought he knew that already. What I do accept, though, is that I am focussed on the value that programs can give, and getting some of that value as early as possible. He sent me a link to the ta...

Beginning Sketchnoting

In September 2017 I attended Ian Johnson 's visual note-taking workshop at DDD East Anglia . For the rest of the day I made sketchnotes, including during Karo Stoltzenburg 's talk on exploratory testing for developers (sketch below), and since then I've been doing it on a regular basis. Karo recently asked whether I'd do a Team Eating (the Linguamatics brown bag lunch thing) on sketchnoting. I did, and this post captures some of what I said. Beginning sketchnoting, then. There's two sides to that: I still regard myself as a beginner at it, and today I'll give you some encouragement and some tips based on my experience, to begin sketchnoting for yourselves. I spend an enormous amount of time in situations where I find it helpful to take notes: testing, talking to colleagues about a problem, reading, 1-1 meetings, project meetings, workshops, conferences, and, and, and, and I could go on. I've long been interested in the approaches I've evol...

Not Strictly for the Birds

One of my chores takes me outside early in the morning and, if I time it right, I get to hear a charming chorus of birdsong from the trees in the gardens down our road, a relaxing layered soundscape of tuneful calls, chatter, and chirrupping. Interestingly, although I can tell from the number and variety of trills that there must be a large number of birds around, they are tricky to spot. I have found that by staring loosely at something, such as the silhouette of a tree's crown against the slowly brightening sky, I see more birds out of the corner of my eye than if I scan to look for them. The reason seems to be that my peripheral vision picks up movement against the wider background that direct inspection can miss. An optometrist I am not, but I do find myself staring at data a great deal, seeking relationships, patterns, or gaps. I idly wondered whether, if I filled my visual field with data, I might be able to exploit my peripheral vision in that quest. I have a wide monito...

ChatGPTesters

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "Why don’t we replace the testers with AI?" We have a good relationship so I feel safe telling you that my instinctive reaction, as a member of the T...

Vanilla Flavour Testing

I have been pairing with a new developer colleague recently. In our last session he asked me "is this normal testing?" saying that he'd never seen anything like it anywhere else that he'd worked. We finished the task we were on and then chatted about his question for a few minutes. This is a short summary of what I said. I would describe myself as context-driven . I don't take the same approach to testing every time, except in a meta way. I try to understand the important questions, who they are important to, and what the constraints on the work are. With that knowledge I look for productive, pragmatic, ways to explore whatever we're looking at to uncover valuable information or find a way to move on. I write test notes as I work in a format that I have found to be useful to me, colleagues, and stakeholders. For me, the notes should clearly state the mission and give a tl;dr summary of the findings and I like them to be public while I'm working not just w...

Build Quality

The Association for Software Testing is crowd-sourcing a book, Navigating the World as a Context-Driven Tester , which aims to provide responses to common questions and statements about testing from a context-driven perspective . It's being edited by Lee Hawkins who is posing questions on Twitter , LinkedIn , Mastodon , Slack , and the AST mailing list and then collating the replies, focusing on practice over theory. I've decided to contribute by answering briefly, and without a lot of editing or crafting, by imagining that I'm speaking to someone in software development who's acting in good faith, cares about their work and mine, but doesn't have much visibility of what testing can be. Perhaps you'd like to join me? --00-- "When the build is green, the product is of sufficient quality to release" An interesting take, and one I wouldn't agree with in gener...

Postman Curlections

My team has been building a new service over the last few months. Until recently all the data it needs has been ingested at startup and our focus has been on the logic that processes the data, architecture, and infrastructure. This week we introduced a couple of new endpoints that enable the creation (through an HTTP POST) and update (PUT) of the fundamental data type (we call it a definition ) that the service operates on. I picked up the task of smoke testing the first implementations. I started out by asking the system under test to show me what it can do by using Postman to submit requests and inspecting the results. It was the kinds of things you'd imagine, including: submit some definitions (of various structure, size, intent, name, identifiers, etc) resubmit the same definitions (identical, sharing keys, with variations, etc) retrieve the submitted definitions (using whatever endpoints exist to show some view of them) compare definitions I submitted fro...

Express, Listen, and Field

Last weekend I participated in the LLandegfan Exploratory Workshop on Testing (LLEWT) 2024, a peer conference in a small parish hall on Anglesey, north Wales. The topic was communication and I shared my sketchnotes and a mind map from the day a few days ago. This post summarises my experience report. Express, Listen, and Field Just about the most hands-on, practical, and valuable training I have ever done was on assertiveness with a local Cambridge coach, Laura Dain . In it she introduced Express, Listen, and Field (ELF), distilled from her experience across many years in the women’s movement, business, and academia. ELF: say your key message clearly and calmly, actively listen to the response, and then focus only on what is relevant to your needs. I blogged a little about it back in 2017 and I've been using it ever since. Assertiveness In a previous role, I was the manager of a test team and organised training for the whole ...

Hiccupps

Search This Blog