Help, yet another release!
By Ronald Korporaal
Nowadays, businesses all rely on ICT. In the logistics sector, they use the term e-logistics. ICT has become a success factor for many logistics businesses. The availability of stable and reliable software is a prerequisite. However, how do you control not only logistics processes, but also the tools to achieve this, namely logistics software?
Product development logistics software
In my previous blog, I wrote about the use of flexible standardized software. Logistics software offering the benefits of a standardized software package, but otherwise fully customizable to the wishes of the client, without any actual custom work. However, in order to keep logistics software stable and up to date, it is essential to ensure that the software is continuously developed on both a functional and technical level. On a functional level, because the logistics landscape is ever-changing and the software should to be adjusted accordingly. On a technical level, because the client should be guaranteed the latest technologies and security updates.
Test driven development
Fear of releases can never be eliminated entirely, however, through structured testing via a safe method, the risks can be reduced to a minimum. At Adaption, we achieve this through test driven development. A development method in which the key objective is continuously testing the application through fixed scenarios.
How does it work
New functionalities are being developed in the development phase. During this development, test scenarios and test programs are written for every new functionality.
Test scenarios consist of the workflows that the user follows while using the application.
Test programs run the test scenarios and automatically test if the functionalities actually work.
Each functionality has its own test scenario and test program that is run on the software at least 4 times a day to test the software. With each new addition to the system, new scenarios and programs are written and added to the automated testing environment. In fact, development and testing actually take place in one single environment. If a functionality turns out to (no longer) be working correctly, this can be tackled early on and the code can be tweaked accordingly.
Functionalities that remain untouched are constantly tested automatically. Newly developed functionalities are also tested manually to ensure they function correctly. If everything works, the release is published. The user can then use all new functionalities and trust that existing functionalities work like they did before.
Test programs are usually written by the developer that creates the software. This creates the risk that when a developer overlooks something, this will slip into both the testing program and the code of the software. Adaption uses special automatic test coders. These coders are not involved in product development and create test programs independently from the developer. This forms an extra measure to safeguard quality and to bring it to a higher level.
Since all functionalities of the logistics software are automatically tested multiple times in each development phase, the chance of the application not functioning anymore after the release is reduced to a minimum. We do this to continuously safeguard the quality of the logistics software.
Benefits of test driven development
Automatic testing guarantees the stability and quality of the logistics software. Since automatic testing already takes place during the development phase, issues can be tackled early on. Potential bugs are discovered during the development phase instead of during or after the release.
Test driven development
Signaling errors immediately
More time for product development
Security & quality
Guaranteed security and quality
Next blog: Successfully implementing logistics software
Research has shown that 80% of all software implementations fail. Often reported causes for failing implementations: unclear set goals, poor project management and insufficiently involving the end user. This results in “implementation stress” before, during and after implementation of logistics software. How do you prevent and manage all factors that contribute to this implementation stress? To find out, read our next blog.
Follow us on LinkedIn to stay up to date on the latest developments of Adaption and the Logistics Cloud Suite.
Over de Auteur
Ronald Korporaal is co-founder of Adaption Business Software. After studying Industrial Engineering and Management Science at Eindhoven University of Technology, he supervised implementations at various logistics companies as a Software Architect. Ronald is interested in business processes and optimally setting up logistics systems.
Flexible standardized software for the logistics industry
A logistics company aims to offer its clients optimal service and to provide a supply chain that is as smooth and efficient as possible. How do you realize this? By using a standard solution, custom made solution or is there another posibility?