Along with learning new business domains as I work on new projects, I also try to pick up new tools and techniques to help my testing. Recently, I’ve started learning more about some tools that help me get a better understanding and view of the app I’m testing.
At Atomic, we all share the pain of writing blog posts to help with our marketing efforts. As well as helping the company, I’ve found that writing a regular blog post also helps me. The obvious benefit is that it improves my writing skills, encouraging me to share my ideas and thoughts in a succinct […]
I’m sure many of you have come across errors like the one above when you are surfing the internet or using an app. Your first reaction might be, “Who tested that?” You know your site and app would never have an error like this in production! Or would it? Here are a few reasons why […]
My last post referenced some issues I’d found when planning a vacation. After taking that vacation, I discovered some more issues.
My vacation is coming up soon, hurrah! This means a lot of planning and booking and surfing and searching to find cool and unusual places to stay and things to do. It also usually means I find some bugs along the way which give me ideas for testing at work.
I’ve given a fair number of talks over the last few years, and I always try to keep improving. Before my recent talk at Beer City Code, I tried a few new things that (based on the feedback I got) worked very well. 1. Watch a recording of yourself giving a talk. If you can […]
Humans are going to use your app, and they are not going to get everything right every time. If and when they make a mistake, how does your app cope? This can be a fertile ground for testers looking for issues, as often the Happy Path case is written first and assumes everything is good, […]
Testing is often thought of as dull and monotonous, yet something that has to be done. However, I’ve found some fun ways to add variety and incorporate extra testing into everyday routines.
Phone simulators are great for helping development move quickly, but they are only simulators. Testing on a real physical device should be part of your workflow.
I recently ran some quick tests to see how accessible a website was. To do this, I used four different techniques which can test for different types of issues.