Related Content
3 Software Testing Lessons from an Unlikely Source With people trying to stay isolated as much as possible due to COVID-19, going to the grocery store suddenly became something to strategize. At least making a plan, prioritizing risk, and being agile are business as usual for software testers. Here are some of the top lessons testers can learn from our current situation. |
||
Defensive Design Strategies to Prevent Flaky Tests Flaky tests could be the result of issues in the code, but more often they are due to assumptions in the test code that lead to non-relatable results. There are many reasons that tests can fail intermittently, and some can be easily avoided by applying good defensive design strategies. It's all about making your code agile. |
||
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. |
||
Building a DevOps Army As you scale DevOps, you need more team members who understand the fundamentals. You could bring in external folks, but they're expensive and in short supply, so start building your DevOps army now by training existing employees. Here's what testers, developers, and IT operations professionals each need to know. |
||
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. |