hey guys; about approaches to testing. im testing a system that's pretty straightforward about it's functionalities, and I've noticed that most UI interactions are done to set parameters to API requests. With this in mind, It though of elaborating a 100% API suite based on the test coverage that I have now with smoke tests. So I'll be able to do 2 things: 1. on the UI smoke flows, stub 100% percent of the tests passing the contracts as stub 2. have 100% API based tests(following whats covered on the smoke suite), and provide this feedback to the BE team (So no flakiness due to UI failure). What do you guys think of this approach?