|
Is All Testing Exploratory? A Slack Takeover with Michael Bolton Thought leaders from the software community are taking over the TechWell Hub for a day to answer questions and engage in conversations. Michael Bolton, a speaker and thought leader in the testing industry, hosted this Slack takeover, which led to discussions about test exploration, tools, and testers as gatekeepers.
|
|
|
Shifting Your Testing: When to Switch Gears Shifting your testing either left or right can meet different needs and improve different aspects. How do you know whether to make a change? Let your test cycles be your guide. Just like when driving a car with a manual transmission, if the engine starts to whine or you’re afraid you’re about to stall out, switching gears may be just what you need.
|
|
|
The Shift-Left Approach to Software Testing The earlier you find out about problems in your code, the less impact they have and the less it costs to remediate them. Therefore, it's helpful to move testing activities earlier in the software development lifecycle—shifting it left in the process timeline. This article explores the shift-left methodology and how you can approach shifting left in your organization.
|
|
|
The Quality Police: Testing like a Law Enforcement Officer After ten years as a police officer, Adrian Oniga became a software tester. He was expecting a dramatic change, but he soon discovered that there are many similarities between testing and police work, including questioning, investigating, exploring, and analyzing. Here are some ways you can test like a law enforcement officer.
|
|
|
Shifting Testing Left Bakes In Quality from the Start “Shift left” is one of the latest buzz terms in software testing. Movements like agile and DevOps recommend that testers shift left, but what does that mean, exactly? Here's how one tester became a believer in the shift-left movement; how he got his team's developers, analysts, designers, and managers on board; and how his entire organization has benefited from the shift.
|
|
|
Let the Agile Manifesto Guide Your Software Testing Although its values are commonly associated with agile software development, the Agile Manifesto applies to all people and teams following the agile mindset, including testers. This article examines the four main values of the Agile Manifesto and reveals how they can bring agility to test efforts—improving quality for your team and your customers.
|
|
|
What IoT and Embedded Device Testers Can Learn from the Volkswagen Emissions Scandal In 2015, it was discovered that Volkswagen had equipped millions of its cars with software to cheat on diesel emissions tests. It was a team of independent testers that uncovered the fraud. Jon Hagar tells testers what they can take away from the scandal and gives some recommendations to consider in order to improve the test industry for IoT and embedded systems.
|
|
|
Demystifying Mobile Testing: Critical Thinking Prevails There are so many testers who think mobile testing is completely different from other types of testing. But there is no need to totally shift their testing paradigm and strategy; mobile testing is not that different after all. This article details the commonalities and differences in testing mobile applications and how lessons learned from testing other applications can be applied to mobile as well.
|
|
|
Heresy! Automation Does Not Require Test Cases Traditionally, automated scripts are derived from existing test cases. But if we divorce the notion of “automation” from the notions of “test cases” and “test scripts,” we can think of automation as a judicious use of technology to help humans do their jobs. This broadens our world to include different tools that can help testers increase coverage, test faster, and detect trends.
|
|
|
Our Experiment in Exploratory Testing: A Case Study Many testers use exploratory testing techniques daily in their normal work. Doron Bar's team wanted to go all in and see if they should make it part of their official procedure. Here, he talks about how they prepared and conducted an experiment comparing exploratory testing to their usual scripted testing. Read on to see the results.
|
|