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 this bug might have made into it production. Read more on “Who Tested That?” Probably Someone Like You…
My last post referenced some issues I’d found when planning a vacation. After taking that vacation, I discovered some more issues. Read more on More Ways to Test – Vacation Bugs…
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. Read more on More Ways to Test – Travel-Inspired Bugs…
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, and then the conditions to catch and deal with exceptions are added onto this. Read more on More Ways to Test – Testing Error Conditions…
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. Read more on More Ways to Test – Using Tea/Coffee Breaks in your Mobile Testing…
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. Read more on More Ways to Test – Alternating Phone Models Per Test Cycle…
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. Read more on Four Web Accessibility Testing Tools/Practices to Start Using Today…
At Atomic, we have multiple projects happening at once, with team sizes ranging from a solo maker to teams of six and up. The teams are also working on different technologies (web, mobile, IOT devices) with different project risks—it might be a quick and dirty MVP, an app for a high-profile event used by tens of thousands, or a complete rewrite of a legacy system.
When projects differ so much in size and scope, how can I estimate the way I help out with my testing expertise and experience? I sat down with one of the managing partners at Atomic to analyze past projects. Our goal was to detect any patterns and figure out how we could use the data to help teams estimate how much time to schedule for me.
Read more on Using Game Titles to Estimate Testing Scope…
I have a variety of machines for running tests: my trusty MacBook Air, a Win10 laptop, a Chromebook, several models of iPhones, and various flavors of Android. And I have VMWare if I need to spin up some VMs for an exotic combination of IE and Windows. So I should be covered.
Read more on More Ways to Test – Peripherals? I’d Forgotten about Those……
Imagine you’re a food critic. You go to a restaurant and eat three courses; your review the next day says simply:
“I did not get food poisoning.”