I was recently asked: “What else is there to test on a phone app when you’ve tested the functionality?” After giving it some thought, I came up with a brief list and thought I’d share that list with a wider audience. 1. Airplane Mode Test to see how your app behaves when there’s no network. […]
When I first started to learn about testing, I found out about test plans. They looked impressive and professional. Many templates were available, with specific figures on how many P1, P2, and P3 defects were allowed before testing could move to a different phase, how many cycles of testing there would be, etc. They even […]
All developers at Atomic do testing, but I have the specialized role of “exploratory tester.” I use my knowledge and experience to find any gaps that the makers missed during their testing. I’m often working on several projects at once, so I need to focus my testing on the most critical areas of an application. […]
The recent furor over the Iowa caucus results where an app caused chaos reminded me of The Nightmare Headline Game, which can be a great technique to assess risk and the level of testing needed. It can also be a fun game to let a team’s imagination run wild. Maybe you’re not writing an app […]
When coming up with data to test out your app, you might get stuck deciding what to enter. We’ve all used our own name and data or the classic “asdf asdf 123.” One way to get creative with your testing is to turn to fairy tales. And there’s a concept we can clearly learn from […]
Recently, our office dishwasher broke. Fingers pointed at me, as I have a talent for breaking things. It really wasn’t me, but it’s not surprising that I was a possible culprit, as I once managed to get myself locked inside one of the restrooms by somehow breaking the lock (don’t ask).
This summer, there was enough interest at Atomic for us to put together a soccer team to play in a local summer league. It was fun (we even had non-players turn up to support), helped bond us together as colleagues, and even provided some learning opportunities that could be used at work.
Last year, I blogged about bugs I’d found when planning a vacation. As it was that time of year for the Michigan Invasion from the grandkids, I realized it was planning and bug-finding time again.
When I started testing websites, I had a list of quick “attacks” that could surface common issues quickly. Now that I’ve been doing more and more testing on mobile devices, I’ve come up with a similar list for them.
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.