Related Content
 |
2 Ways Developers Can Contribute to Better Testing Testers need to find important information about product quality and present it in a way that can be acted upon. As the people building the software, developers are in a great position to observe the product. By monitoring the test environment and conducting unit testing, they can help inform about product quality. |
|
 |
How to Get Security Groups to Join Your DevSecOps Journey DevSecOps shifts security practices left and assures earlier that your application isn't vulnerable to breaches. But convincing a security group to get on board with your DevSecOps journey may not be an easy task. These four points can help you prove to your security group that DevSecOps is in everyone’s best interest. |
|
 |
Choosing a Font for Software with a Global Audience As more businesses are establishing a worldwide presence, our approach to software must consider globalization and localization. So when it comes to designing the user interface for our apps and websites, we must consider good typography. Here's what to take into account when choosing fonts for international products. |
|
 |
How DevOps Has Changed the Landscape of Testing The focus on automation and “continuous everything,” from integration, deployment, and now all the buzz about continuous testing, makes the daily activities of a tester in DevOps challenging. Testers may be used to controlling quality—or thinking they do—but they need to pivot to assuring their teams focus on quality. |
|
 |
Testing When There Are No Testers More and more companies are shifting toward having their developers responsible for product quality. But how do you conduct good testing when there are no testers? The key is to optimize efforts. Here are some of the fundamentals of testing that your developers should understand, as well as some skills they'll need. |
|
 |
Overcoming Test-Driven Damage Some say test-driven development may work well initially, but as soon as we start to refactor our code, it breaks old tests and requires us to write new ones. This is not the fault of TDD; it’s the way we’re using it. TDD remains a valuable way to verify code as we write it, so we need to repair our test-driven damage. |
|
 |
The Present and Future of AI: A Slack Takeover with Raj Subramanian Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Raj Subramanian, who works with self-healing, AI-based test automation, hosted this Slack takeover to discuss all aspects of AI: testing it, its biases, where it is now, and where it's going. |
|
 |
Take Credit for Your Risk Management Activities If you have an important implementation date, early identification of the minimum viable product is a vital risk-management step that helps focus your team’s attention on what's important. Rather than apologizing for intelligent phasing of functionality to manage risk, explain it to stakeholders and take credit. |
