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

Popular posts from this blog

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 first person to discov…

Kali Linux 101

Linux was always a bit too 'geeky' thing for me. My recent time on bench provided me however with time and motivation to go into this "terra incognita".
The intention was originally to learn some foundations of security testing. After a while I discovered that Kali Linux could provide also benefits for the everyday testing routine. Following is a simple set of tools that will support and enhance your testing.
whatweb Whatweb is a web scanner which provides information about the technologies used on the website, mail addresses found and many more
Example (type into terminal in Kali Linux): whatweb 0-v https://www.houseoftest.rocks/


whois  Provides domain and legal information about the target website (where is it registered, owner, address, etc.)
Example: whois houseoftest.rocks



cewl Outputs all the words contained in the target website. You never know when such feature comes handy. You can output also into a file of course. Example: cewl https://www.houseoftest.ro…

Thrown into automation

Situation & Problem I was thrown into an automation test project.

Concretely test automation of 3 different applications (different in purpose, look, structure, behavior) which regression testing was covered only by a automation test suite that was written in AutoIt and the size of the code was quite complex and huge for a new person in the automation.
Well, that was not the problem, it is a description of the situation.

The problems weren't initially visible. I was never automating before, so I needed to learn quite a bit of the code & got to know all the applications that were part of the project.

The problems were not so appealing at the start, but I would formulate then as: Maintenance of the scripts took too longBy new versions of the application, it took some time to adjust the scripts to the changesThis caused delay in information flow from testers to managers & developersThe changes in the application were not clearly communicated to testersTesting was purely t…