Remove Culture Remove Engineering Culture Remove Test-Driven Development 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. These principles tell us our tests should be: Fast.

Testing 130
article thumbnail

A Software Engineering Career Ladder

James Shore

What I’m really doing is changing the engineering culture at OpenSesame. Culture doesn’t change easily. I’m hoping this will help direct people to new behaviors, which will in turn start to change the engineering culture. Bigger than a breadbox, anyway. It tends to snap back. This makes room for a lot more skills.

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

Functional vs non-functional software testing

CircleCI

When you think of software testing, what comes up first? For many developers, unit tests and integration tests are often top of mind. Both software testing methods are vital to writing and maintaining a high-quality production codebase. What is functional testing? Integration testing. Unit testing.

article thumbnail

Build cloud infrastructure from your CI pipeline with Pulumi

CircleCI

Cloud engineering brings the cloud closer to application development, applying engineering practices and principles to infrastructure and innovating and collaborating faster across the entire team. Pulumi is an infrastructure as code platform you can use to help create a cloud engineering culture in your organization.

article thumbnail

6 Crucial Issues for Legacy.NET App Modernization

Datavail

Establishing an IT culture. Modernizing legacy applications is the perfect opportunity to reform your broader IT and engineering culture as well. Consider establishing internal coding standards that will make testing and long-term maintenance easier.

Azure 52