Related Content
 |
A Culture of Criticism in Software Companies Author Qaiser Munir outlines his experience with the culture of blame in software development toward those considered to be responsible for "quality". |
|
 |
Reaping the True Value of Exploratory Testing Exploratory testing best practices should be accommodated for and communicated upfront, with early stakeholder buy in in order to ensure you get the most from your efforts. |
|
 |
Balancing Testing and Delivery Times in Software Development So how can developers and their teams optimize testing procedures with the modern tools and tech available to them? Here, we will explore optimizing testing through experimentation to meet delivery deadlines and adapt to challenges in software development.
|
|
 |
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. |
|
 |
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. |
|
 |
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. |
