Related Content
 |
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. |
|
 |
When Buying New Software, Make Sure You're Getting What You Really Need The first step in any significant software procurement is to assure there is a clear definition of the business problem being solved. If you don’t know what you want, you aren’t prepared to negotiate for it, so you'll end up with a system or tool that isn't what you need—and you'll likely be disappointed at delivery. |
|
 |
How to Get Started Automating Your API Tests When designing a test automation strategy, an area that is often overlooked is automating API testing. API test scripts are faster and easier to write than other types of scripts and can be fairly simple tests. An added benefit is that API testing can be included in your continuous integration tools for quick feedback. |
|
 |
Embedding Performance Engineering into Continuous Integration and Delivery In the world of continuous integration and continuous delivery, the importance of ensuring good performance has increased immensely. While functional and unit testing are relatively easier to integrate into these processes, performance engineering has typically raised more challenges. Here's how you can mitigate them. |
|
 |
Testing the Requirements: A Guide to Requirements Analysis Everyone knows testing requirements is important, and everyone says they do it, but it seems like no one knows exactly how. The best way to solve this problem is to introduce a requirements analysis stage that has to be done before coding starts. No one knows a product as well as a tester who works with it every day! |
|
 |
Application Release Automation: Why the QA Pro Should Care The speed of testing depends on a consistent software release process that can provide critical information when reporting issues. QA pros will benefit from a new set of DevOps tooling called application release automation, which drives continuous release deployment and provides visibility about what was deployed. |
|
 |
Interface Grief: Is It Agile, or Just Bad Software Engineering? There are people who will use "being agile" to justify software engineering practices that could be perceived as lazy or even bad. The specifications are going to change, they say, so it would be a waste to engineer more to begin with than the minimum viable product. What's expediency and what's just poor practice? |
|
 |
Balancing Process and Tools The limits of a tool may lead us to realize that we are not working as effectively as we can, and often, changing a tool is part of the solution. But there are good and bad ways to select a tool and how you use it. In particular there are risks when you focus first on tools before considering the problem. |
