This blog describes the MeetUp trend in Testing, attending and hosting them
This blog describes the ALF annual summit in London, why it is different in approach to other conferences, and what value conferences provide.
At the Agile North East Lightning Talks Competition I had 8 minutes to tell a room full of people how to help testers succeed.
After 18 months testing FX trading software I decided to create and share a heuristic cheat sheet to help explore trading apps.
Fiddler's AutoResponder is a great tool to mock API Responses when you're testing front end logic. It's simple but provides some powerful testing options. This is a short post to show you how.
How I used R to collect and analyse all of the tweets made about Test Bash Manchester, a recent software testing conference.
I was lucky enough to attend Test Bash Manchester recently. This is my first hand report of the experience. Find out what happened when testers from around the world all came together to talk about testing.
Having never given a technical talk before, I agreed to speak in public then found myself figuring out how I was going to do this.
I developed a web application to enable exploration of the data collected by a survey of software testers. I explain how R and Shiny can be used to create reactive web applications which make data accessible to a wider audience.
Continuing my research into Software Testers I examine how and why people are getting into testing careers and present a snapshot of testers in 2016
Custom locators are great for when you need to roll your own, but they can require some tweaking when an application starts to get more complex. Here I'll look at how to chain custom locators.
I decided to do some research into testers and the challenges we face in the work place to find some answers. These are some my findings.
Test metrics have for too long been the 'Holy Grail' of determining quality. This blog post looks at the reason why the metric of 'defect density' should perhaps have a second thought before use to determine software and tester quality.
Automation of user interactions in browsers can be difficult. Even more so when you have to hunt for elements in a single page application. How can we ensure reliable location of these and reduce flaky checking?
How to stay fresh, focused and super effective when testing alone
Some of the biggest challenges when testing software can be getting the software into some very specific states...
When automating end to end browser verification, how do you keep it simple, make it robust and enable flexibility within your automated checks. One way is to use helpers.
Six annoyingly awkward bug patterns that every tester should know...
Web testing, in simple terms, is checking your web application for potential bugs before the system is revealed to the public. When testing web applications, there are many different resources you can use to help your testing. But a great resource is browser developer tools which can help in many...
This is the second post in a series of simple and short tutorials for automating tests using Protractor. In this post we will look at the difference between isPresent and isDisplayed, and we will use getText and the matchers toContain and toEqual to create some tests.
This is the first post in a series of simple and short tutorials for automating tests using Protractor. In this post we will look at how to find page elements using the Chrome developer tools, and writing a simple test using the Jasmine matcher isDisplayed.
Testers by themselves can't find all the bugs. Nor identify all the problems. So how do you get non-testers to look critically at the software and organise them to be effective at it. At least for day. This post explores the bug hunt. Asking the questions, giving some tips.
When deciding which tests to automate, one criteria commonly used is to identify simple repetitive tasks that are performed often. This morning while completing my bacon sandwich order form I realised that this was a relatively simple task that I repeat each Friday morning.
How we develop software has changed dramatically, more so in the last 8 years since smartphones came to prominence. How software is tested, arguably hasn’t. Or has changed so much, that some don’t see the need for testers at all.
When Malcolm Gladwell wrote a book called Blink about the power of the subconscious in 2005, a heuristic was named for it. Read on for how blink testing works, and some further thoughts on how other ideas the book contained can influence your testing.
There are many ways of testing software within an Agile methodology, here are 7 things I learned.
It has become generally accepted that a good project has a set of automated tests behind it - whether they be unit tests, integration tests or end-to-end tests. However I don’t often hear people talking about the benefits vs cost and how much should be spent on particular projects. I...
Should there be testing standards. If so, who should define them, and how should you access them?
Writing end-to-end tests for a Single Page Application (SPA) built with Angular or Knockout, and how to improve the robustness of those tests.
Which school, which certificate? It’s a minefield for testers. Are any certifications worthwhile?
This is the start of a testing journey for Scott Logic, where we will share some testing experiences, expertise and examples.
Betamax is a tool to help with testing applications that consume web services by allowing the developer to record responses and then replay them. In this post we look at how we can use it in Scala.
Introduction Less.js can be run in two ways, firstly through node and secondly in the browser. A great deal of the code is shared, but not all of it - particularly the way it deals with imports, paths and url's differs. Whilst typing "make test" in the node less.js repository...