Software maintenance & software testing

If you have ever set up a software to meet your business needs, you know the satisfaction you feel when you get to the point that things just work. Great! Give yourself a high five! Time to celebrate – but don’t turn the page and move on forever. The same goes for when you drive your new car off the lot. Feels good! But you know that if you neglect oil changes, you’re setting yourself up for disaster down the road.

The more simple the tool, the simpler the maintenance. The maintenance that hand saw requires is no comparison to a CNC, but the CNC generates far more dollars for your business.

The more capabilities the software has, the more you can make it work the way you want it to. When you do this, you may be using the software differently than the next guy – He might be using the exact same software but has set it up differently. Multiply this by thousands (or millions) of users with the same software – all with individual setups, hardware, networks, languages … the list goes on. This capacity to adapt your software to your specific processes is a powerful advantage that feeds into what makes your business different from the next shop, but it also becomes something that needs to be managed.

When new versions of the software are released, everyone’s experience might be a little, or a lot, different. It can take some digging and testing in order to find what’s working and what’s not. It takes some learning to understand new features and new possibilities. It might even seem tempting to skip it and continue using the version that’s humming along nicely, but this plan is not sustainable. At some point, you realize you’ve been left behind and then end up with an urgent and significant hurdle to tackle if you want to catch up.

So maybe just wait for others to test out the new version and try and hop on board later when most of the kinks have been worked out, right? This is true when you keep your settings really basic. But for more demanding configurations, this might not be the best strategy. The best time to start testing is when the new version is released.

This is the time to find things that are not working well with your particular setup. This is the time when fixing these issues is fresh in the developers minds and they are available to fix them. If you rely on others to test, then there might be issues that do not affect others but that do affect your setup.

The testing phase is not volunteer work you’re doing for the sake of the software company, but rather it’s a way to get a head start with the software developer and ensure the issues that might arise in your particular setup are not overlooked. Testing ensures your issues get attention so that you can transition to the new version with as much ease and success as possible.

There typically is a lot of testing that’s done before the release of a new version, but testing that happens directly in the market cannot be replicated in-house. In your businesses is where the rubber hits the road. This is where the software gets exposed to all the different scenarios and this is when the squeaky wheels get the grease. Just like the continuous learning on software never ends, neither should refining it to better suit your business. By transitioning to every version you have a smaller number of changes to adapt each year. Keeping up with the new versions of your software will help you avoid down-time trying to catch up on several changes that happen when you wait several versions.

Cabinet Vision has a new version each year that runs side by side with older versions. The older version of Cabinet Vision remaining intact for daily production while you test new features on the new version. In New Zealand, Joinery IT assist businesses to implement new versions, utilising new features where possible and delivering software add-ons for new hardware supplied to market.

Contact Philip Smith at Joinery IT on 021 201 4450 to learn more about software testing without disrupting production.