1 min read

Day #47 | You are responsible for third-party dependencies

When you use a third-party dependency for your software app, be sure to have automated tests to test their expected output.
Day #47 | You are responsible for third-party dependencies

If your software app relies on a third-party software/service. Always, test them frequently. Validate that the output from the dependencies is accurate.

You have (almost) no control over third-party software dependencies. Yes, some of them are open source. Yes, they may have a lot of stars. Yes, they can get new releases every week.

But you can never 100% guarantee that software always works with no bugs or crashes. Worst if you don’t even know how the internal works of those dependencies.

Yes, you don’t have to use dependencies.

But using them to make your job usually easier.

Don’t re-invent the wheel if you don’t have to.

But, if you use another wheel, you are responsible for it.

So when you use a third-party dependency for your software app, be sure to have automated tests to test their expected output.