Process
Articles
DevOps: Changing the Software Testing Game The DevOps movement promises to be as influential as project management and good requirements ever were in programming and testing. By combining ops (deploys, monitoring) with programming (automated builds, automated virtual servers) and testing (risk management), we get something that is more than the sum of its parts. |
||
Get Smart about Your Regression Tests’ Value If you aren’t measuring the coverage your regression tests provide, you may be spending too much time for little benefit. Consider the value of your regression tests as you create and manage them. You need to be smart about the regression tests you maintain in order to gain the maximum value from the work put into creating, running, and analyzing their results. |
||
Accountability in Testing Embedded and IoT Software Systems Take a look at the critical systems in the world today and you’ll find software. From water, power, and utilities to nuclear plants, factories, and cars, pretty much everything has become integrated with digital devices and the internet. We need to do testing from a risk-based perspective and be accountable to the public by acknowledging what is tested and what is not. |
||
Containers: A Tester's Friend or Foe? Containers support the timely delivery of a quality software application. However, the change to a DevOps process involving containers will require testers to adapt to this new, more agile environment. What does that mean for testers and the work they do? Here's how testers can embrace these changes, containers, and DevOps. |
||
Testers: An Integral Part of the DevOps Team Building innovative software faster and better is imperative to an organization’s success, so it makes sense to take advantage of DevOps. But what some teams fail to consider is that testing is a crucial part of the process. Without a “test early and often” mentality, DevOps would only be able to release software faster—not better. |
||
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. |
||
Using Key Performance Indicators in the Transition from Legacy Systems Switching from a legacy system to a composite application can be tricky: The transition will require a lot of restructuring. To be sure you’re conducting the most streamlined, complete transfer possible, focus on key performance indicators. Defining KPIs can help prioritize objectives and create an efficient new workflow. |
||
IoT, Mobile, and Tech Curve Disillusionment: Moving beyond the Hype The hype around the Internet of Things is at its peak. Should you bother learning the skills developers and testers require in this new field, or will it soon become just another trend that's fallen out of favor? Jon Hagar makes a strong case for why the IoT will be relevant even after the clamor dies down, and why its associated skills will serve you well no matter what. |
||
Does Domain Expertise Really Matter? Many job descriptions include a requirement for domain expertise to filter candidates for testing jobs. But is expertise really necessary before joining a team? Does it ensure a good tester? Justin Rohrman digs into his experiences in difficult business domains, what expertise means, and how it applies to software testing. |
||
Accepting the Tester into the DevOps Fold Today’s tester has moved upstream, along with the test processes, where he is involved right from the product design stages. This can create great opportunities for the team to bond, but if not handled well, it can become a breeding ground for strained relations. Adopting DevOps means promoting collaboration. |