Docker: How to Stop and Remove All Containers at Once

It’s an understatement to say that Docker is a game-changer for systems engineers and developers. You can run almost any application with a single command and customize it for your environment via a consistent container-based interface. But as containers proliferate, controlling them gets more complicated, too. Managing containers from the command line can be painful, but setting up an orchestration tool like Kubernetes or Docker Swarm is overkill for smaller systems.
Stopping and removing a container from the command line takes two steps. Stopping and removing two containers is four. And stopping and removing 10 containers is—well, you get the idea. Check out this post from Eric Goebelbecker on CloudBees’ blog to look at how to make the Docker command line easier to use.

Feature Testing: Everything You Need to Know

How do you think about testing a new feature? If you’re a developer, your mind probably immediately jumps to things like automated unit tests. If you’re a product manager, the first thought that pops into your head might be manual QA testing. As an operations manager, your mind might jump to regression testing to ensure you won’t have to roll back a feature or bug fix after deployment. In reality, all these approaches, and more, are critical parts of testing a new feature. When you roll out new code, you want to make sure it works right. The hard part is ensuring that you’re spending the right amount of time and energy testing that code. Spend too little, and it’s likely that you’ll ship a product riddled with bugs and sporting features that don’t work. Learn all the ins and out from Eric Boersma on CloudBees’ blog.

Sprint Scheduling Explained: How to Make a Sprint Schedule

The main event during agile methodology is the sprint, the stage where ideas turn into innovation and valuable products come to life. On one hand, agile sprints can be highly effective and collaborative. At the same time, they can be chaotic and inefficient if they lack proper planning and guidance. And for this reason, making a sprint schedule is one of the most important things you can do to ensure that your efforts are successful. If you’re looking to schedule your next sprint, check out this post from Justin Reynolds on Plutora’s blog.

Test Strategy vs Test Plan: Managing QA in the Enterprise

We also updated a post this week. The software testing world sometimes includes too much confusing jargon. Many expressions sound similar but refer to different concepts. The “test strategy vs. test plan” dilemma is a good example. What is the meaning of each one of those terms? Why do you need them? How do they differ? And what are their similarities? These are the kinds of questions this post on Testim’s blog will answer.