Skip to main content

Testers toolkit

As every craftsman needs his tools, testers are no exceptions.

I was this weekend at SOCRATES SWITZERLAND (SOftware CRAftsmanship and TESting) where we talked also about useful everyday tools.

This list tries to be as general as possible to provide tools which can be useful to most part of everyday work, more specialised test-useful tools are very context dependent. I use most of the tools mentioned here and believe they can provide value also to you.

Documenting

  • Screenshot - good picture is worth thousand words, this applies especially for testing, the following are some screenshotting tools and editors I used and can recommend
    • Lightscreen - simple tool for capturing pictures, free, cannot edit the pictures
    • FastStone - screen capturing tool and editor, cheap & gets the job done
    • Snagit - very powerful screen capturing tool and graphic editor, many functions which you never knew you can do, but wont be able to live without afterwards, a bit pricey
  • Recording (Flashback Express) - well and a recording is worth a thousand pictures. This tool provides a very good platform for recording, sharing and viewing. It can record also keystrokes and has a very lightweigt format for storing these recordings (for this you need to set up a blank desktop background)
  • Text editor (Sublime or Notepad++) - keeping track of your test notes or writing drafts of some test planing requires a good distraction free, extendable text editor. I have used both of these and they do the task ideally

General helpers

  • Breevy (Textexpander for Mac) - usefull tool for text abbreviation and also launcher of apps, just set up an abbreviation for your frequently used words or application and observe how it replaces these when typing in any application
  • KeePass (also LaspPass or 1password) - have all your passwords in one place + remember mostly just one password
  • uBlock Origin - younger brother to Adblock and Adblock+, advisable mostly because his older brothers lost osme of their vigilance. Keep in mind that if you testing websites that this app can interfere (assuming some users use adblockers I would advise to test sometimes also with this turned on)
  • IFTTT, Nuzzel - Lets face it, everybody uses some social media parallel in their work,  this service provider helps you to automate some predictable processes around it and save you time
  • Fences, Deskscapes - bring some order to your desktop, organise icons into fences and set some cool wallpaper order

Productivity

  • Brain.fm (or Noisly, respectively playlists on Google Play, Spotify, etc) - basically music to improve your focus in work or for help with relaxation after a stressful meeting
  • Pomodoro technique (and useful timer) - aimed at increasing productivity through time-boxing your work. Useful also in context of SBTM
  • Keep track of the spot you left before break - developers advise leaving with one red unit test, I would advise leave an unsubmitted bug report before you leave (you can always look at it with fresher eyes) - of course if its not a critical one;)

Scripting/Coding

Not every tester must know how to code, but many do, here are some general usefull tools to help
  • Shells - not everybody likes the default option of shell provided by your OS, I got some recommendations
  • Diff programs - not only developers have the need to compare text or files for differences, ehre are some useful tools for it

Other

  • Bikablo - not directly a tool, but a guide how to write impressive graphic elements on flipcharts and whiteboards, usefull at workshops and presentations


Comments

Post a Comment

Popular posts from this blog

When to start automation?

If you are asking this as a tester, you probably asking too late. Automation is something that can save you some portion of your work (understand resources for your client) and i rarely found cases of testing work that did not need at least some portion of automation. I know that it is rarely understood that automation is something to be developed & maintained and if you cover enough of the application, you do not need any more regression - well i do not think that somebody has done an automation regression suite that if fully reliable (i am not speaking about maintaining this code - which is another topic). There can be always a bug (or quality issue) that slips through, even when you scripts go through the afflicted part. I understand that many testers have no development background or skills, but i doubt the developers that could help you are far away. I am not assuming that they can do the scripts for you.... However if they understand what you need, they can say how e
4 comments
Read more

Testing impact on security

... or the impact when testing is lacking? Security breaches , hacks , exploits , major ransomware attacks - their frequency seem to increase recently. These can result in financial, credibility and data loss, and increasingly the endangerment of human lives. I don't want to propose that testing will always prevent these situations. There were probably testers present (and I'm sure often also security testers) when such systems were created. I think that there was simply a general lack of risk-awareness on these projects. There are many tools and techniques from  a pure technical point of view to harden the software in security context. Some of them have automated scans which crawl through your website and might discover the low hanging fruits of security weaknesses ( ZAP , Burpsuite ...), without much technical knowledge from the person operating it. The more important aspect is however the mindset with which you approach the product. The tester is often the f
Post a Comment
Read more

RST Explored - My experience

My experience report from my recent RST Class I attended the RST class after a while, wanting to refresh my knowledge about the RST view on testing. It was a 4-day event, each day 3 Sessions, approx 4hour/day. My general impression was that it enriched and refreshed my understanding of testing.   Each of the four days had an central theme Day 1: "It is possible to test everything?" Day2: "When to stop testing? How to test from specifications." Day3: "Product coverage outline. Complexity of the system" Day4: "Risk analysis and coverage"   Going deeper into the topics of each day would be impossible without spoilers, I will therefore rather focus on my impressions and what this training has brought me. The way Michael was guiding us through the class was very engaging, although we usually started with a short lecture, questions and remarks were encouraged from start and we had an shared review after each exercise - students explaining their work,
Post a Comment
Read more