Related Content
 |
Shifting Security Left in Your Continuous Testing Pipeline Security is often the black sheep of testing—an afterthought that gets only a scan before release. We have to make security a first-class testing citizen with full-lifecycle support. For the best impact, introduce security testing into the early phases of the continuous testing pipeline. Here are some tools to help. |
|
 |
Strategically Using Slack Time after a Release When you've worked for months on a big software release, afterward you may want to jump into the next project. But building in some slack time between sprints is a good idea. After a big release, there will probably be more work as new users discover bugs in your software. Plan for some more testing and development. |
|
 |
Building Levels of Testing in Software Development Quality is now considered everyone's responsibility, and many developers are acquiring testing skills to validate their code before it gets to dedicated quality engineers. But where should you start? Consider beginning with unit tests that help you write better code, then building to integration tests and E2E testing. |
|
 |
Why UX Is More Important Than Coding When it comes to your project succeeding, the quality of the code is secondary to user experience. That's because software is all about making users' jobs easier. If you start coding in a vacuum without understanding what your users need to do, you can't be sure you’re making the right thing. You need UX research. |
|
 |
8 Questions to Ask before Fixing a Defect Some defects require a fix, without a doubt. But not all defects are created equal, so careful thought should be applied before a defect is fixed. The goal isn’t to fix every reported defect; it’s to return value to the customer and profit to the company. These eight questions can help in the decision-making process. |
|
 |
Figuring Out Your Regression Testing Strategy When your application is scheduled to go to production, the development team may be asked what their regression testing strategy is. This is a perfectly reasonable question, but a lot of people have a hard time answering it. Don't overcomplicate it. Analyze your process, look at the other testing, and put it together. |
|
 |
Reality-Driven Testing in Agile Projects Agile teams can drive down rework and devise more useful tests quicker by prioritizing reality-driven testing. This means tests based on reality, or relevant test activities above and beyond those derived from requirements. Learn some strategies to get real and design tests to locate important bugs that truly matter. |
|
 |
Quality Engineering in Agile and DevOps Ensuring that quality is advocated for at every step along the lifecycle can be tough. One easy response is, “Quality is everyone’s job”—after all, whole-team accountability is a key tenet of agile. But what does this really mean in practice? What approaches and roles help us embrace a culture of quality engineering? |
