An automated test suite with 100% code coverage is the goal…

… but what if you haven’t had time and let the technical debt build up?

It takes discipline

That might mean having to enforce the rules via CI, Notifications, pre-commit Git hooks… Photo Credit: Qusai Akoud be.net/qusaiportfolio

Code confidence lets you run faster

With improved tests comes confidence in your code. And with code confidence comes the ability to iterate, fix, and experiment a lot faster. You need to have confidence that your change isn’t going to knock out the other half of the system. This does rely heavily on the quality of your tests so it’s not something you’ll achieve overnight.

Give youself a headstart

It may sound daunting, but there are ways to give youself a headstart.

Keeping up motivation

Even if you implemented all of the above, there is still a danger to slip back into old ways and slowly watch that code coverage percentage drop. Especially when you have hotfixes coming in, little “tweaks” that you don’t think needs coverage, or even just time pressures of moving onto the next feature.

Slack can be a useful way to keep visibility on all of your repos each time a test is ran.

Only The Paranoid Apps Survive

On a mission to make Salesforce the platform of choice for enterprise mobile apps

Francis Hart

Written by

iOS & macOS Developer. Tech enthusiast. 🚀 Software Engineer at @MobileCaddyOrg. Creator of http://sketchkey.co http://mediaexplorerapp.com http://urlyapp.com

Only The Paranoid Apps Survive

On a mission to make Salesforce the platform of choice for enterprise mobile apps