loading...

Discussion on: Practical Software Testing Ideas

Collapse
dennmart profile image
Dennis Martinez

This is solid advice, especially with fixing broken builds as soon as possible. I've seen test suites with broken builds for weeks with no one doing a thing about it because "there's no time", which is a lousy excuse.

One thing I don't particularly agree with in this article is where you mention backend tests are better than frontend tests. It all depends on your application. I've worked on applications with excellent test coverage on the backend and lots of bugs sneaked through out testing pipeline because of the frontend. Depending on your application, I'd argue over spending a little more time on UI tests if your time is very limited, because it will cover more than just the backend.

Also, I would add that keeping your tests running fast is essential. Minimize overhead like too many database connections, mock external services when it makes sense, etc. If your tests are too slow, devs will stop paying attention to them and your test suite will break down quickly.

In any case, this is a great article with a lot of good tips for developers and testers to improve their testing skills!

Collapse
aviaryan profile image
Avi Aryan Author

Thanks, Dennis. You mention valid points.

Depending on your application, I'd argue over spending a little more time on UI tests if your time is very limited, because it will cover more than just the backend.

I didn't look it this way. Agreed.

Also, I would add that keeping your tests running fast is essential. Minimize overhead like too many database connections, mock external services when it makes sense, etc. If your tests are too slow, devs will stop paying attention to them and your test suite will break down quickly.

Good point. I should have included this. :)