Related Content
 |
Software Features to Avoid in a Production Environment When developing an application, it’s best practice not to use certain software features in a production environment. These include features related to programming language, the OS, the database, a framework, a web or application server, or a tool. You have to consider the production setup to avoid bugs or server crashes. |
|
 |
Ditch Your Logs for Better Monitoring Metrics Many teams use logs to track the behavior of applications, services, or platforms. But how actionable is that log data? There are better ways to parse that information and make it more visible, more useful, and easier to understand. Try converting your logs into metrics for a faster and more lightweight monitoring system. |
|
 |
Testing in the Dark Requirements only go so far in identifying areas to test. Sometimes testers are given no information at all, leaving it up to them to determine what to test. Don’t accept the need to indiscriminately test with no clear understanding. Your testing should be targeted, and these techniques will help focus your test effort. |
|
 |
Leave No Tester Behind Creating comprehensive automated tests within a sprint can be a challenge. If the testers don't finish the automation and the rest of the team moves on, testers get left behind and can't catch up. You need some techniques to keep everyone together and ensure that all essential work is accomplished—including test automation. |
|
 |
Comparing 4 Top Cross-Browser Testing Frameworks The market is flooded with cross-browser testing frameworks, with more options than ever before. How should you decide which option is best to test your application for compatibility with different web browsers? Let’s take a look at four of the top open source solutions today and compare their benefits and drawbacks. |
|
 |
The Evolution of Modern Testing: A Slack Takeover with Adam Sandman Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Adam Sandman, director of technology at Inflectra, hosted this Slack takeover and discussed the main challenges testers face today, what modern users expect, and how to approach test automation. |
|
 |
5 Pitfalls to Avoid When Developing AI Tools Developing a tool that runs on artificial intelligence is mostly about training a machine with data. But you can’t just feed it information and expect AI to wave a magic wand and produce results. The type of data sets you use and how you use them to train the tool are important. Here are five pitfalls to be wary of. |
|
 |
Code Integration: When Moving Slowly Actually Has More Risk Many decisions about code branching models are made in the name of managing risk, and teams sometimes pick models that make integration harder in the name of safety. Moving slowly and placing barriers to change can seem safer, but agile teams work best when they acknowledge that there is also risk in deferring change. |
