Skip to main content

Test engineering

Sometimes investing is a feature-rich test framework is a good idea, but starting lean is the best place to start - tests run as part of CI/CD should always be as lean as possible. Packages are there too help you, just be selective and conscious of potential overheads.

less is more

Conversely, don’t waste too much time on native coding - packages are there too help you, just be selective and conscious of potential overheads created on the Build server.

Scope of automation is not just about verifying feature for you web or mobile app. That is just the window on the testing input from business viewpoint, but the test automation scope is more dynamic than this. Or should be.

I do often repeat the same mantras: exploratory testing is a mindset that can be applied to automation, you don’t need to run a heavy load test to get useful feedback, web accessibility should be covered by default (any excuses are poor excuses), security testing is an essential not an option, device/browser compatibility testing should be approached with scope caution.

Importantly, all tests of all kinds should evolve constantly, or they are most likely useless.

Including non-functional tests earlier

You can waste a lot of time focusing on trapping functional errors, but these hold little value in comparisron to testing for performance issues. You don’t need to run a heavy load test to get useful feedback, and developers find these tests useful.

book an intro meeting

Hire me

If you like what you’ve read and think we’d work well together, I’d love to hear from you.

Contact me now →