Related Content
Making DevOps Evolution Happen It takes effort to evolve an organization’s culture, processes, and technology to optimize performance for a DevOps environment, and it all comes down to the people. Large-scale mobilization requires a focus on people at all levels, empowering them to discover and make the changes that will help them most. Here's how. |
||
Are Your Fundamentals Malfunctioning? Every objective has certain elements that are fundamental to its success. These include the supporting tasks or systems that we take for granted but without which our “real” work could not get done. In order for any organization or team to meet its primary objectives, these fundamentals need to be functioning properly. |
||
Smart Testers Adopt Smart Automation As technology continues to evolve, questions around the role of quality also continue. Is manual testing still required? What should the role of automation be? Where are we heading with quality? Smart testers hoping to develop their careers will have to brush up on their exposure and expertise and embrace automation. |
||
When to Use Different Types of NoSQL Databases Web-scale data requirements are greater than at a single organization, and data is not always in a structured format. NoSQL databases are a good choice for a larger scale because they're flexible in format, structure, and schema. Let’s explore different kinds of NoSQL databases and when it’s appropriate to use each. |
||
A Simple Rule of Thumb for Unit Testing There's a simple rule for the minimum values testers should explore: “none, one, some”—or, how the software behaves if you send it nothing, one thing, or some set greater than one. It's not comprehensive, but it gives a good feel for how the feature works at the moment. Developers can also use this in unit testing. |
||
5 Steps to Stable Continuous Testing in DevOps Continuous testing minimizes risk and ensures DevOps has the tools to deliver quality, modern code that is ready for the future. To fulfill this, you have to first understand the three types of personas in testing. Then, you'll know how to work with them to progress along the path toward achieving continuous testing. |
||
Are Your Retrospectives Adding Value to Your Scrum Team? Sprint retrospectives are often skipped, compressed, or organized in a way that doesn't provide good feedback. This is unfortunate, as a well-planned retrospective is a great way to improve how you work. Good retrospectives enable engagement and safety, distill and prioritize ideas, and create concrete action items. |
||
Using Agile to Navigate through Medical Device Regulations When you test medical device software, you must be very careful. But when development wants to push a cadence of two weeks per sprint, every sprint, you’ve just got to keep up! Interpret the regulatory requirements not as a set of disabling constraints, but as a challenge to find the optimal route to navigate through. |