Remove Continuous Delivery Remove Engineering Culture Remove Testing
article thumbnail

5 ways to do Continuously Improved Testing

Xebia

In many organizations, automated testing lags behind and becomes a bottleneck for successful continuous delivery. Either tests do not provide enough confidence or companies take a very traditional approach, resulting in releases either introducing substantial risks or becoming costly. Prerequisites. Independent.

article thumbnail

Nurturing Design in Your Software Engineering Culture

Strategic Tech

There’s huge variety between those two extremes, and there’s also a point where too much focus on design and not enough on delivery is hugely counter-productive as well. Both valuing design and striving for continuous delivery are necessary. They prefer to work in isolation and just deliver. It can be a cost-effective approach.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Article: Using Machine Learning for Fast Test Feedback to Developers and Test Suite Optimization

InfoQ Culture Methods

Software testing, especially in large scale projects, is a time intensive process. Test suites may be computationally expensive, compete with each other for available hardware, or simply be so large as to cause considerable delay until their results are available.

article thumbnail

Is the Paved Road right for you?

Xebia

This could include building the code, testing, building images, scanning the images for vulnerabilities and, finally, publishing those images. You can run code compliance checks, unit tests, and even test the Docker images as part of your pipeline. Find out how easily the code can be built and tested. Conclusion.

article thumbnail

The Spotify Model of Scaling – Spotify Doesn’t Use It, Neither Should You

Agile Pain Relief Notes from a Tool User

E.g. A developer reports to a dev manager; a tester to test manager, etc. Instead, focus on the things that Spotify had going underneath the hood: Delivering Value – all improvements to the system should be tested by asking: Does this improvement/experiment, help us deliver value? Yes, it is, but it’s a different kind of matrix.

Agile 124
article thumbnail

Improve your Functional Monitoring with the Functional Monitoring Quadrants

Xebia

Functional monitoring is a crucial part of any successful Continuous Delivery implementation. Synthetic Testing versus Real User Activity. With Synthetic Testing, we continuously get information about the availability of the system. We create these tests to detect issues fast and predictably. Conclusion.

Metrics 130
article thumbnail

Platform Engineering Essentials: 5 Key Learnings Before You Start

Xebia

Test that the capabilities you want to deliver are actually desired by the teams. Gaging early if teams are eager to onboard is your first test if your platform is feasible. Build a pl atform b ased on an actual need. One form of approach could be to deliver one capability quickly to onboard teams onto, and then expand from there.