When discussing agile and its impact on the industry, the concept of the “traditional testing role” is often a topic of conversation. However, we shouldn’t just assume that this “traditional” tester is as common as we seem to make it sound, as testers have always had to do more than just test.
A long-time freelancer in the tech industry, Josiah Renaudin is now a web content producer and writer for TechWell, StickyMinds, and Better Software magazine. Previously, he wrote for popular video game journalism websites like GameSpot, IGN, and Paste Magazine, where he published reviews, interviews, and long-form features. Josiah has been immersed in games since he was young, but more than anything, he enjoys covering the tech industry at large.
All Stories by Josiah Renaudin
In a perfect world, developers and testers are constantly asking themselves, “How can I make this more secure?” Security has become both a hot topic and a major priority in most businesses, but actually creating a mobile or web application that’s not porous might be more difficult than ever.
Change isn’t always necessary—or even good, for that matter—but when is it actually the right time to incorporate a new tool, language, or piece of technology that might be taking the market by storm into your business? How do you identify the risks?
That little rectangular device sitting in your pocket can already do so much, so it’s not as if there’s some terrible drought of innovation in the mobile space. But according to AppDiff.com’s CEO, Jason Arbon, the white hot excitement stemming from mobile phones has cooled.
Better collaboration, adaptive planning, early delivery, and constant improvement—do any of these agile pillars sound like something a non-software team would want to avoid? Agile has its place in different companies and teams across a multitude of industries.
Just because something is new, shiny, and more fully featured doesn’t mean that everyone is going to want to use it. Even if your IoT-enabled smart grill is voice-activated, it still has to be both consistently functional and as easy to use as a regular grill.
Some form of automation should be used to streamline testing, but leveraging automation as a crutch won’t help you or your team spot every bug and produce high-quality software. In automation, the tools don’t do all the testing—they simply do what they are told to do by the actual tester.