Imagine: No Code Changes. What To Automate?

Here’s a thought: With applications tying into so many other apps, endpoints, services and databases, it can be difficult to know what should be automated.

Imagine if your app’s code wasn’t changed at all for a month. Assuming it was working before, it should still work, right?

And yet, how often do tests fail because of something upstream not working properly.

What would you need to automate to detect that problem early? And: would it even really need to be a test againstĀ your app, or more of a health check againstĀ theirs?

Would that be a pretty simple test? Probably.

Then: If you already have some tests that cover this, what about running those first? Make sure everything upstream of you is up and reasonably functioning, before running the rest of your tests.



One thought on “Imagine: No Code Changes. What To Automate?

  1. Thanks for the article.
    My two cents. We have had tests in the past which tested the middle API layer(RESTful services). So these automated tests were run separately as part of other projects and not necessarily as health check but then it later got implemented as such. There was a dashboard which shows status of these test results. Maybe the next step could have been to run your regular GUI automated based on status of API tests as part of overall CI cycle.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s