Related Content
 |
Making Testing Visible Most testing work is invisible—something that happens inside your head and leaves no artifacts behind. This generally leaves testers feeling like no one understands what they do all day. Here are some ideas for collaborating with your coworkers so they can see—and start to understand—your testing work. |
|
 |
Crowdsourcing Emerging Manufacturing and Water Security Technology Borrowing from the successful NASA Challenges playbook, the US Department of Energy recently launched several crowdsourcing efforts to incentivize new applications and technologies in additive manufacturing, also known as 3D printing, and transforming nontraditional water sources into resources. |
|
 |
4 Ways to Verify Developers’ Skills for a Job Interview Developers often struggle to convey their skills effectively during a job interview, making it difficult to assess their capability. But you want assurance that a candidate who has an impressive CV actually has the practical abilities you need. Here are four ways of verifying developer applicants’ skills. |
|
 |
Agile and DevOps Bring the Focus Back on Quality As companies move to agile and DevOps, silos are coming down and there is more interaction and collaboration among teams. Quality is also becoming everyone's responsibility for the entire software development lifecycle. Quality is more than just testing: Consider a quality value stream along the overall value chain. |
|
 |
The Cost of Software Testing Testing is regarded as the number one bottleneck in the software delivery process. Most people simply conclude that developers are value centers, and testers are cost centers. But developers' work also brings cost, and—more importantly—testers' work also brings value. It's time to reframe our thinking about testing. |
|
 |
A New Approach to Load Testing with Browser-Level Users Since the inception of load testing, the approach has been mostly the same: simulate the traffic of an application by creating load at the API level. But there have been market shifts that make load testing with browser-level users more feasible—allowing us to test with real load and measure true user performance. |
|
 |
Making Continuous Integration Work for You Many developers learn about using continuous integration to improve their deliverability speed and decrease the amount of effort needed to launch new features. Actually practicing continuous integration, however, is nowhere near as straightforward as it sounds. Here's how to get started in making CI work for you. |
|
 |
Continuous Testing Is Not Automation Many people confuse continuous testing with test automation. That makes sense, because you cannot do continuous testing without automated tests. But it is much more. Continuous testing has a higher-level maturity that could require a totally different way of working—but it also gives a faster path to production. |
