The best way to make people depend on your work is to make them think that you know what they will need. The post is based on a remarkable book written by Chad Fowler, The Passionate Programmer.
On a daily standup, the project owner states the idea that it would be good to have a ready smoke automated test for integration with external application services. And you say that it is already running as part of the CI system.
How to predict such a request? In Heuristic Test Strategy Model [Bach], you have coverage for every possible software testing request. Using this document, you can start practicing predicting offers and ideas. Before every sprint, write three things about software testing that has not been done yet. At the end of the sprint, check the results. After some time, start to implement your sprint guesses. But be careful about overkills. Do not put aside your committed work, at the start do this in your free time. The safest approach is to announce your guesses at the beginning of the sprint. Soon, your guesses will become your regular software testing practice.