Related Content
 |
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. |
|
 |
Testing at 43,000 Feet: Reporting Risk That Matters Many teams' daily testing gets broken down into numbers. If you're used to dashboards, it can be easy to forget the prime objective: to raise up quality issues—or, in the case of safety-critical devices, potential hazards. Graphs are comfortable, but do they really provide the information we should be looking for? |
|
 |
Why the Burden of Security Should Be Assumed by the Entire Team Quality can be improved over time, and while it’s difficult to change perception, it’s still possible. But poor security can sink your ship before it even leaves the dock. Invest in the security of your application and be sure to spread that responsibility to multiple levels of your software team. |
|
 |
Security Is Critical, So Why Don’t We Take It Seriously? Once you move into banking applications or anything related to healthcare, it becomes more and more important for developers and testers to guarantee that all the data they’re gathering from their users is locked behind the biggest, most bulletproof safe you’ve ever seen. |
|
 |
Using Feature Flags to Boost Testing and Deployment A feature flag is a configuration setting that lets you turn a given feature on or off. There is no need for a feature to be complete before you can start testing—as soon as the first piece of code is merged, you can turn the flag on in your test environment and begin. This also reduces risk. Do you use feature flags? |
|
 |
3 Major Continuous Delivery Hurdles Teams Need to Overcome Teams that leverage continuous delivery and continuous integration are playing an entirely different game than software teams of the past—instead of mapping out this major, ridged timeline, data is being both gathered and used more frequently (and effectively) than before. |
|
 |
What Testers Need to Know about Security Every single tester should keep an eye on what security vulnerabilities might be plaguing their testing, but speaking in an interview at STARWEST 2016, Jeff Payne, the CEO and founder of Coveros, explained why you need to put a focus on security very early in the process. |
|
 |
The Value of Testing Simply People obsess over the number of tests and test coverage, but tests that cover more code don’t always improve quality. Some tests have low value and thus, implicitly, high cost. Simple tests may not seem impressive at first glance. But the goal of testing is to ensure quality, and simple tests can be very valuable. |
