Appvance Insights

Here we share thoughts and observations about what matters most to our customers from experts at Appvance and our partner companies. We welcome your comments and feedback.

Velocity, Meet Quality: Why DevOps must define QA as Code

Velocity, Meet Quality: Why DevOps must define QA as Code You’ve heard of pair programming and test-first development. You’ve heard of agile software development. You’ve heard of continuous integration, daily builds and continuous delivery. You’ve heard of infrastructure as code. These keystone practices make possible a DevOps culture of continuous (daily, weekly, monthly or regularly…

Details

Video: How Does DevOps Impact QA?

Video: How Does DevOps Impact QA?

Bringing a DevOps culture into an enterprise requires at its core a 10X speed increase in QA. this webinar investigates the new concept of Unified Testing, where a use case can be re-used across multiple test types by QA team members.

 

Approaching Implementation

Approaching Implementation

By Brad Egeland, Originally published in BradEgland.com

No matter how smoothly things have gone on your project up till this point, as you approach implementation you’ll feel at least two things: relief and anxiety.  Relief because it’s nearly over and you’re still moving forward. Anxiety because it’s nearly over and there may be something—or some things—that you’ve overlooked. How you manage the project—including your team and your customer—can help out a lot on that common feeling of anxiety and that “have I done everything I need to do” moment of truth. But there are things you really know deep down that you must do in order to really feel comfortable as you roll out the new tech solution to your anxiously awaiting customer and their end users.

Details