Atmel Corporation has enhanced the quality of its software testing worldwide and established best practices for automation for all 1500 IT developers in the organization.
Software tests can now be implemented across all countries and in days instead of months. Eficode Praqma has matured the test method Continuous Delivery and lifted it from the Norwegian division of Atmel to the entire corporate group.
When you turn on your radio, TV, mobile phone or electric toothbrush there is a high probability that it is equipped with intelligent microtechnology from the worldwide Atmel Corporation. The group develops and manufactures microcontrollers for both consumer and industrial solutions, all with the aim of creating solutions that make everyday life and work easier and smarter.
The Atmel Corporation has a large IT development spread over many countries, which develops software for the development environment that customers buy with microcontrollers. Customers use this environment to develop their own software solutions into their products, so that their electric toothbrush can vibrate and their mobile phone touchscreens work.
The tools group in Atmel produces and integrates new software drivers and plug-ins every single day. However, testing them took a long time - except in Norway, where the IT organization had implemented the open source tool ‘Jenkins CI’ with the purpose of automating software testing.
“We have to stay one step ahead in order to maintain the competitiveness throughout the organization. In Norway, the results with automation were compelling and therefore the corporate management asked us to roll out these methods to other locations. IT Operations expanded the infrastructure in order to be able to support more volume and we were recommended to contact the Danish company Eficode Praqma as the specialist who could handle the job”, says Per Arnold Blåsmo, Senior Software Craftsman, Atmel Norway.
With Eficode Praqma as close adviser since 2012, Atmel Corporation has, with Continuous Delivery, automated all test processes worldwide and is able to deliver new software versions all the way to the customers. At the same time, the operation of all IT systems was centralized.
“First of all, we’ve increased quality of the software we provide significantly. We have established best practices and can both develop faster and release software more frequently. Where before it took months to release, it now takes only a few days in the whole group. In addition, we are now able to test large installations across the different countries”, says Per Arnold Blåsmo, Senior Software Craftsman, Atmel Norway.
The cooperation with Eficode Praqma proved very important for Atmel Corporation.
“We couldn’t find a local consulting firm that could do the job.But the company that leads the Jenkins CI development recommended Eficode Praqma as the most competent knowledge center in our part of the world. We have been very pleased with the collaboration from the start. They are extremely knowledgeable and quick to understand our challenges. Therefore, we have a good and close relationship with Eficode Praqma, which we hope will continue for many years to come”, says Per Arnold Blåsmo, Senior Software Craftsman, Atmel Norway.
What testing steps should you include in your Continuous Delivery pipeline? Don’t just string together existing manual processes - use simple, collaborative tools to design something better!
A new card game to design Continuous Delivery pipelines
Continuous Delivery and DevOps are here to stay and not because they’re being practiced by trendsetting unicorn companies. The fact is science tells us that these approaches work and this year’s conference gave us lots of examples.
Continuous Delivery and DevOps - Not Just For Unicorns
A developer that pushes their changes and goes on a celebratory walk to the water cooler is done. But, they’re not done done, their changes have yet to be thoroughly tested, added to future release notes, properly peer reviewed and more. These are pains we want to rid the software industry of, and here’s how we do it.
How we tell the Continuous Delivery story
Immutable infrastructure as code reduces inconsistency and makes deployments faster and easier. We can provision immutable infrastructure with Packer & Terraform. Let’s use them to provision Jenkins Windows build slaves.
An immutable infrastructure approach
The Continuous Delivery and DevOps Conference took place in Stockholm for the third time. It brought together scientists, thought leaders, and practitioners to share their experiences and thoughts on CoDe and DevOps.
Inspiring approaches to Continuous Delivery & DevOps
Only a year ago, I was a CoDe Academy student learning about Git, Docker and Jenkins. This year I’m teaching Docker to 24 students at CoDe Academy 2017 in Aarhus.
Falling in love with Everything as Code and Automation
Hear about upcoming events in Scandinavia, latest tech blogs, and training in the field of Continuous Delivery and DevOps