beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ismaël Mejía (JIRA) <>
Subject [jira] [Commented] (BEAM-1499) Update testing documentation at beam-site
Date Thu, 16 Feb 2017 20:48:41 GMT


Ismaël Mejía commented on BEAM-1499:

Yes, of course, I will be following this issue and will try to add what I understand or improve
what you do. I started this discussion with Stas (and Kenneth) because I was a bit lost about
the use of the categories in particular for the tests of the IOs, where I found for example
that DatastoreV1Test uses RunnableOnService, BigQueryIOTest uses both NeedsRunner and RunnableOnService
and BigTableIOTest uses none. So I was quite lost. And I have the impression we are just copy
pasting and not explaining clearly what is the goal of having tests in Categories, as well
as the existing Categories.

> Update testing documentation at beam-site
> -----------------------------------------
>                 Key: BEAM-1499
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: website
>            Reporter: Stas Levin
>            Assignee: Jason Kuster
>            Priority: Minor
> The [testing section|] could use some updates
in light of the ongoing development in the test utils department.
> Some examples:
> * Working with {{TestPipeline}} and its features (purpose, best practices):
> ** Enforcements
> ** Auto run
> * API surface tests
> * {{@RunnableOnService}} vs {{@NeedsRunner}}

This message was sent by Atlassian JIRA

View raw message