An evolving idea of something I call the QA Fortress

Author Vanja Žunić
Category Development
Date Nov 22, 2018
3 min read

As a member of Bornfight’s QA team, I come face to face with many diverse tools, so I decided to group them and create the QA Fortress.

In Bornfight, I constantly work with and discover new tools. One day I decided to put them all on paper, and after I was done, I had around 30 different tools on the list. After that I structured them a little bit better, and also connected them by categories and groups. That ultimately become the QA (Quality Assurance) Fortress, as I like to call it.

Creating a mental map

To create the mental map, I decided to use a web tool called MindMup.

First I created a group called Tools. I placed all of the tools I came across in it, along with their purpose and a link to the official page. After that, I connected those Tools with a group I called Helpy Stuff – that’s also a list of tools, but I called them like that because they are supportive to those “main” tools in my line of work. Many of them have comprehensive uses, but I just use them for some particular purposes. For example, Screaming Frog SEO Spider tool is, how a name indicates,  an “SEO tool”, but I use it to get a list of all pages with a 404 response code, so I can then check inline links for those pages and try to find an answer why this is happening.

Expanding the idea

Then I came up with the idea of extracting parts of official documentations from those tools (for my purpose and uses), and called it Local Documentation. This is basically a simple document with the usage information for any specific tool. See, it’s not an unusual thing for a user to check some tool’s documentation, just to get lost in a sea of information. And all they needed was some basic information on making the tool work. That’s why I created Local Documentation.

From there, the entire structure grows even more by adding a Logging and Monitoring node. The idea behind it is to collect logs and reports from appended projects/products, and to structure them using a visualization tool for the monitoring process.

One additional node in the QA Fortress structure is called Support HQ (headquarter). It’s a place for every additional thing you need to keep in mind while you’re working on projects. There are nodes like Security and Vulnerability, Accessibility, Blockchain, Types of testing approaches and Heuristic Testing Strategy sheets.

On the bottom of the MindMup structure, we can see the part called Simple new project flow and Simple new project flow example. In them, as the names are suggesting, I placed the flow and an example of this flow. It’s used in situations where a new project appears, and has all the steps for creating a sustainable place for the observation and nurturing of that project/product.

It’s only the beginning

Today, the QA Fortress is much more than it was when I started. There is so much more to do, and also a lot of space to do it, so feel free to visit my public Github repo and express yourself. All ideas are welcome – let’s create an environment and a community that helps each other by sharing experience and knowledge!

Check out the full Github repo about the QA Fortress.

__________

Want to become a part of our Quality Assurance team? Send us your application!