Related Content
 |
The Cost of Software Testing Testing is regarded as the number one bottleneck in the software delivery process. Most people simply conclude that developers are value centers, and testers are cost centers. But developers' work also brings cost, and—more importantly—testers' work also brings value. It's time to reframe our thinking about testing. |
|
 |
A New Approach to Load Testing with Browser-Level Users Since the inception of load testing, the approach has been mostly the same: simulate the traffic of an application by creating load at the API level. But there have been market shifts that make load testing with browser-level users more feasible—allowing us to test with real load and measure true user performance. |
|
 |
Making Continuous Integration Work for You Many developers learn about using continuous integration to improve their deliverability speed and decrease the amount of effort needed to launch new features. Actually practicing continuous integration, however, is nowhere near as straightforward as it sounds. Here's how to get started in making CI work for you. |
|
 |
Continuous Testing Is Not Automation Many people confuse continuous testing with test automation. That makes sense, because you cannot do continuous testing without automated tests. But it is much more. Continuous testing has a higher-level maturity that could require a totally different way of working—but it also gives a faster path to production. |
|
 |
Implementing Continuous Delivery in the Federal Government Federal agencies generally have more regulation, slower processes, and a command-and-control style of bureaucracy. How does it work when trying to foster agility and implement a continuous delivery model? Gene Gotimer relates his experiences and challenges with encouraging a culture change in federal government. |
|
 |
Lessons Learned (and Unlearned) at STARCANADA 2018 With a week full of sessions, tutorials, training classes, and events, the STARCANADA software testing conference had plenty of takeaways. Some highlights: what jobs will look like in the future with AI, why testers should lead efforts to make quality everyone's responsibility, and the importance of unlearning. |
|
 |
Solo Programming, Pairing, and Mobbing: Which Is Right for You? Programming often is considered an individual pursuit, but there are other options gaining popularity: pairing, where you work with another developer or tester, and mobbing, where the entire team works on one thing at a time. Each is effective for certain kinds of challenges. How much collaboration is right for you? |
|
 |
How Are You Managing Your Test Debt? Just as debt can be good and bad in everyday life (such as a home mortgage), debt in the engineering world can also be good and bad. This applies to quality engineering as well—with good and bad test debt. As testers, how do we create a balance and stay at the right test-debt quotient? |
