Related Content
 |
Test, Test, Test Test, test, test. This is a phrase that has caught everyone’s attention this year as we grapple to mitigate COVID-19. The WHO states that testing is the only way out, as we cannot fight the pandemic blindfolded. |
|
 |
A Physical Metaphor for Quick Fixes and Root Cause Analysis If you deal with legacy code you’ve likely found yourself struggling to debug and fix a mysterious, intermittent problem. Along the way you may have discovered some code that didn’t quite make sense. |
|
 |
Comparing PHP and Java PHP and Java are both languages ranked in the Top 10 in the TIOBE index. In this article, we compare the two languages. PHP is an interpreted language. The Zend Engine that is bundled with the PHP distribution is a scripting engine that interprets PHP scripts as a user has developed them. |
|
 |
3 Critical Considerations for Technical Due Diligence Technical due diligence is the process of verifying a company’s technical capabilities, quality, and processes. It is typically performed by investors or buyers before a contract. There are many aspects you can investigate, but three are crucial: a code review, security evaluation, and open source components compliance. |
|
 |
Immunizing Your Software against a Defect Pandemic When your released software is infected with problems, there is the possibility of a pandemic defect, when a wide geographic area and an exceptionally high proportion of the end-user population is affected. Just like with the coronavirus, following proper guidelines and taking mitigation steps can reduce the spread. |
|
 |
The Layers in the Test Automation Journey Test automation is not just a bunch of automated scripts to be written and handed off. The scripting process, though important, is just an inner layer embedded deep within the whole. There are several more layers that are important in showcasing the true value of the automated scripts. You need to understand all layers. |
|
 |
What’s the Problem with User Stories? Agile projects focus on very lightweight, simple requirements embodied in user stories. However, there are some problems with relying solely on user stories. They often don't contain enough accuracy for development, testing, or industry regulations. There's a better way to write detailed requirements that are still agile. |
|
 |
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. |
