Related Content
 |
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. |
|
 |
Comparing Java and Ruby Java and Ruby are both open source languages, and both are ranked in the top 20 of the TIOBE index for most popular programming languages. If you want to learn a new language and are trying to decide between these two, let’s explore common differences in syntax and constructs to discover which may be more useful for you. |
|
 |
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. |
|
 |
Comparing Ruby and PHP Ruby and PHP are both open source languages, and both are ranked in the top 20 of the TIOBE index for most popular programming languages. If you want to learn a new language and are trying to decide between these two, let’s explore common differences in syntax and constructs to discover which may be more useful for you. |
|
 |
2 Familiar Problems for Software Developers In the quest for writing good code and delivering the right thing to customers, developers have several challenges. But most of them can be boiled down to two main problems: discovering the real scope, and how to do the work. Interestingly, they’re very similar to the problems faced by testers and others in non-dev roles. |
|
 |
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. |
|
 |
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. |
