Cool; will be good to have and make things clearer! On Tue, May 25, 2021 at 2:39 PM Kyle Weaver <[email protected]> wrote:
> I left some comments. In summary, I think this is mostly a documentation > problem. If running a test isn't as easy as "./gradlew > $MODULE:integrationTest", there should be instructions in the test class's > javadoc. > > On Tue, May 25, 2021 at 2:05 PM Udi Meiri <[email protected]> wrote: > >> My first place to go would be here: >> https://cwiki.apache.org/confluence/display/BEAM/Java+Tips (although it >> doesn't document your use-case) >> >> You are right that finding the correct gradle task or jenkins job is not >> straightforward. >> >> >> On Tue, May 25, 2021 at 12:48 PM Alex Amato <[email protected]> wrote: >> >>> Friendly ping. I'll wait for more suggestions by the end of the week. >>> Then close it out. >>> >>> ---------- Forwarded message --------- >>> From: Alex Amato <[email protected]> >>> Date: Fri, May 21, 2021 at 2:54 PM >>> Subject: One Pager - Test Command Line Discoverability in Beam >>> To: dev <[email protected]> >>> >>> >>> Hi, I have had some issues determining how to run Beam tests. I have >>> written a one pager for review and would like your feedback, to solve the >>> problem >>> <https://docs.google.com/document/d/1qGkBmHUOIVM2KfPyKhJL6oH2nAgX9Vkl0z9ZydEoWzA/edit> >>> : >>> >>> "A Beam developer is looking at a test file, such as >>> “BigQueryTornadoesIT.java” and wants to run this test. But they do not know >>> the command line they need to type to run this test." >>> >>> I would like your feedback, to get toward a more concrete proposal. A >>> few solutions are possible for this, mentioned in the proposal. But any >>> solution that makes it very easy to understand how to run the test is a >>> viable option as well. >>> >>> Cheers, >>> Alex >>> >>
