Since the move to Build Kite, community developers no longer have access to see why their builds fail when an Elastic member runs /test.

It would be very helpful if the developer of the integration can see what error messages have spawned so that they can be fixed instead of waiting on a response from an Elastic member to share the error details. This will decrease time to release if error messages on build can be revealed. The other solution is ensure all tests can be executed locally using elastic-package: elastic/elastic-package#1721