While on my reflective bender on my QA work over the year I decided to cover the actual processes we have in place at work. So, I wrote a blog post outlining the processes we have in place at Chirpify today, on the official Chirpify blog.
My last post was an overview, but this one will dive into some of the problems I encountered when I was first getting started as the de-facto quality stakeholder and dig into what REALLY mattered when it came to the actual process of QA. Fitting into the development cycle is critical.
There is no better way to learn the workflow than to follow a feature through the factory and out the door. Make it a priority to see a feature from design to deploy as soon as possible.
Every team has idiosyncrasies that make experience a better teacher than a ReadMe.
When I was hired on my job description clearly included committing actual code so I also had the advantage of being able to make several early commits and deploys that far and away gave me a better idea than just being told. Do this if you can.
Once you know the workflow, agile or not, you can get a better picture of where QA fits. Almost always at the end of a cycle, but often interspersed with development under certain conditions. If your team uses a kanban board, a flow chart, a spreadsheet, or project management software the next step is to carve out a QA section and OWN IT. This is your wheelhouse, and when a ticket or a story enters it it must bend to your will.
If having a QA engineer/Tester/Test Engineer wasn’t part of the teams workflow, or if testing was less of a process that was owned and more of a vague responsibility placed on each developer… then the workflow will need to change. You’ll be the catalyst here.
In order for your work to be effective you’ll need to start asking for things to happen upstream, long before they land in your lap. One of the best ways is to get your hands into the ticket/story system and outline steps that need to happen as that ticket is passed along to a developer. If your lucky like me, buy in from your manager here will be easy and they’ll be eager to help make that happen.
One of the simplest process wins early on was to simply request that every dev write a few short summary of how the feature should work, how it shouldn’t work, and finally how they had tested it.
Now you know how the “Happy Path” was tested (or if it was tested at all..) and you can immediately compare this summary with the feature spec in the story and make sure nothing was missed.
I was very skittish about walking into a new team, a new workflow, a new product, and a new codebase and then starting to make demands to make my life easier.
You need to suppress that doubting voice, ultimately you were hired to improve the product and build a process that makes more stability a foregone conclusion.
At a startup the only constant is change and you can rest easy knowing your changes will be the least of anyones concerns. As long as you explain the benefits of your decisions people are normally more than happy to hear the initiative being taken.
If you’re building a QA process for a startup then you are also the key stakeholder for Quality and by fiat you now have the opportunity to start instilling good habits. Don’t hesitate to advocate from a place of confidence if you know your changes will result in a higher quality end result.
When your team members start to reap the benefits of better quality any prior doubts will be washed away.
This year marked the first full year of QA at the startup I work at, working as the first QA hire on an existing engineering team. There were a lot of challenges, but I wanted to share some of my take aways and challenges that were overcome.
There was not a system in place for me to plug into when I arrived, testing was happening, deploys were happening, and code reviews were happening all somewhat organically and maybe haphazardly.
I had what amounted to a clean slate and worked to build up some systems from there.
My first step was to learn the product. The most important thing i’ve done since I started last year was to become a product expert. Knowing our product intimately continues to be one of the best values I bring to the table and allows me to be more targeted and succinct in testing.
As the product grew I also began to maintain documents outlining a lot of the more esoteric behavior, outside of repo ReadMes. This has saved my hair more than a few times.
My second step was to integrate myself into the Dev team workflow. Finding out where QA lives in the release lifecycle is important and defines a lot of the actual QA work that gets done. In our semi-agile team framework QA became the last step on the Kanban board. I like to think of that part of the board as ‘active development part II‘. In an ideal state i’m working hand in hand with the devs assigning and closing out bug tickets until we have a stable feature.
The third step was deciding on tools. We use Asana as our management software, ticketing system, and QA tracker. I’ve enjoyed using it as I’ve reinvented the QA ticket process several times because it affords a lot of flexibility in the organizational structure of your tasks (tickets).
I use Google Apps for spreadsheets, where I document feature behavior, or maintain checklists that are shared with third parties.
And I use CasperJS to automate a lot smoke testing that would otherwise eat a huge amount of my time.
I’m still searching for a good lightweight tool to organize functional test cases, an essential part of reducing the bus-factor of the QA team (1).
If I had to describe my year in one word it would be: Iterative
I haven’t built the best QA system, nor the best processes, but in the last year they’ve grown to better match the challenges we have everyday. The next year will be even (iteratively) better.
As shown by the frequency of updates to this blog my focus has been squarely elsewhere since the beginning of the year, but i’ve got a good excuse. I promise.
At the start of this year I began working as a QA Engineer at an exciting start up in Portland and i’ve barely had a chance to stop and catch my breath since. Rereading my last post I realize that I still have the same goals, but I need to be smarter about giving myself the room and prioritizing my time in order to be successful. I’d like to have a killer #DevYear, but i’d also like to crush it at work as a QA Engineer.
How do you set aside time to grow? It helps if you like what you do, and I do. But beyond that simply saying that you’ll apply yourself when free time presents itself isn’t enough.
My goals are heavily anchored around projects, realistic and attainable projects that achieve things I want for myself and require me to grow in areas I desperately want to. If I have a project as opposed to a learning goal I can schedule time and adhere to it much more strictly and quantifiably.
The culmination of that is in two large ongoing projects: An online magazine and a web application.
By focusing my work around these projects instead of a nebulous goal like “I’d like to become proficient at [insert skill here]” I have created deliverables for myself.
I plan to really grow my skills in the following areas by executing on these projects:
Just as i’m agile in the workplace I plan to be agile in my implementation of these personal projects. An MVP for the web app and Magazine to be debuted sooner than later. Watch this space.
Talk to you soon,
Johann
Johann Hannesson 