[jira] [Commented] (BEAM-1499) Update testing documentation at beam-site
[
https://issues.apache.org/jira/browse/BEAM-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946310#comment-15946310
]
Jason Kuster commented on BEAM-1499:
There was some more discussion and I had some more thoughts on it today -- I'm
going to hold off doing any work here until things settle down.
> Update testing documentation at beam-site
> -
>
> Key: BEAM-1499
> URL: https://issues.apache.org/jira/browse/BEAM-1499
> Project: Beam
> Issue Type: Improvement
> Components: website
>Reporter: Stas Levin
>Assignee: Jason Kuster
>Priority: Minor
>
> The [testing section|https://beam.apache.org/contribute/testing/] 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
(v6.3.15#6346)
[jira] [Commented] (BEAM-1499) Update testing documentation at beam-site
[
https://issues.apache.org/jira/browse/BEAM-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15944993#comment-15944993
]
Stas Levin commented on BEAM-1499:
--
[~jasonkuster], we can add some info following the change of
{{RunnableOnSerivce}} to {{VerifiesRunner}} and the respective
[dev-thread|https://lists.apache.org/thread.html/188595475ec2576929d6a1de87086436a973c564421d6e67e91c2f7a@%3Cdev.beam.apache.org%3E].
> Update testing documentation at beam-site
> -
>
> Key: BEAM-1499
> URL: https://issues.apache.org/jira/browse/BEAM-1499
> Project: Beam
> Issue Type: Improvement
> Components: website
>Reporter: Stas Levin
>Assignee: Jason Kuster
>Priority: Minor
>
> The [testing section|https://beam.apache.org/contribute/testing/] 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
(v6.3.15#6346)
[jira] [Commented] (BEAM-1499) Update testing documentation at beam-site
[
https://issues.apache.org/jira/browse/BEAM-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15933101#comment-15933101
]
Davor Bonaci commented on BEAM-1499:
Is this done?
> Update testing documentation at beam-site
> -
>
> Key: BEAM-1499
> URL: https://issues.apache.org/jira/browse/BEAM-1499
> Project: Beam
> Issue Type: Improvement
> Components: website
>Reporter: Stas Levin
>Assignee: Jason Kuster
>Priority: Minor
>
> The [testing section|https://beam.apache.org/contribute/testing/] 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
(v6.3.15#6346)
[jira] [Commented] (BEAM-1499) Update testing documentation at beam-site
[
https://issues.apache.org/jira/browse/BEAM-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15882918#comment-15882918
]
Stas Levin commented on BEAM-1499:
--
[~jasonkuster], I've added two paragraphs under the contribute/testing section:
"Effective use of the TestPipeline JUnit rule" and "API Surface testing".
Please feel free to let me know if you have any comments.
> Update testing documentation at beam-site
> -
>
> Key: BEAM-1499
> URL: https://issues.apache.org/jira/browse/BEAM-1499
> Project: Beam
> Issue Type: Improvement
> Components: website
>Reporter: Stas Levin
>Assignee: Jason Kuster
>Priority: Minor
>
> The [testing section|https://beam.apache.org/contribute/testing/] 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
(v6.3.15#6346)
[jira] [Commented] (BEAM-1499) Update testing documentation at beam-site
[
https://issues.apache.org/jira/browse/BEAM-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15873270#comment-15873270
]
Stas Levin commented on BEAM-1499:
--
[~davor], sure thing. Thanks for helping out!
Looking forward to get this section updated as I have recently been made aware
that there are a few dark corners here and there :)
> Update testing documentation at beam-site
> -
>
> Key: BEAM-1499
> URL: https://issues.apache.org/jira/browse/BEAM-1499
> Project: Beam
> Issue Type: Improvement
> Components: website
>Reporter: Stas Levin
>Assignee: Jason Kuster
>Priority: Minor
>
> The [testing section|https://beam.apache.org/contribute/testing/] 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
(v6.3.15#6346)
[jira] [Commented] (BEAM-1499) Update testing documentation at beam-site
[
https://issues.apache.org/jira/browse/BEAM-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870832#comment-15870832
]
Davor Bonaci commented on BEAM-1499:
Oh, sorry, [~staslev] -- you are more than welcome to tackle this. I
incorrectly inferred that you are looking for someone to do it and just wanted
to help find someone. Again, sorry. Please take it away as you see fit.
> Update testing documentation at beam-site
> -
>
> Key: BEAM-1499
> URL: https://issues.apache.org/jira/browse/BEAM-1499
> Project: Beam
> Issue Type: Improvement
> Components: website
>Reporter: Stas Levin
>Assignee: Jason Kuster
>Priority: Minor
>
> The [testing section|https://beam.apache.org/contribute/testing/] 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
(v6.3.15#6346)
[jira] [Commented] (BEAM-1499) Update testing documentation at beam-site
[
https://issues.apache.org/jira/browse/BEAM-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870667#comment-15870667
]
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: https://issues.apache.org/jira/browse/BEAM-1499
> Project: Beam
> Issue Type: Improvement
> Components: website
>Reporter: Stas Levin
>Assignee: Jason Kuster
>Priority: Minor
>
> The [testing section|https://beam.apache.org/contribute/testing/] 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
(v6.3.15#6346)
[jira] [Commented] (BEAM-1499) Update testing documentation at beam-site
[
https://issues.apache.org/jira/browse/BEAM-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870539#comment-15870539
]
Stas Levin commented on BEAM-1499:
--
I'd be glad to lend a hand as well, just say the word :)
> Update testing documentation at beam-site
> -
>
> Key: BEAM-1499
> URL: https://issues.apache.org/jira/browse/BEAM-1499
> Project: Beam
> Issue Type: Improvement
> Components: website
>Reporter: Stas Levin
>Assignee: Jason Kuster
>Priority: Minor
>
> The [testing section|https://beam.apache.org/contribute/testing/] 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
(v6.3.15#6346)
[jira] [Commented] (BEAM-1499) Update testing documentation at beam-site
[
https://issues.apache.org/jira/browse/BEAM-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15870300#comment-15870300
]
Davor Bonaci commented on BEAM-1499:
[~jasonkuster], I think you'd be the best person to tackle this ;-)
> Update testing documentation at beam-site
> -
>
> Key: BEAM-1499
> URL: https://issues.apache.org/jira/browse/BEAM-1499
> Project: Beam
> Issue Type: Improvement
> Components: website
>Reporter: Stas Levin
>Assignee: Jason Kuster
>Priority: Minor
>
> The [testing section|https://beam.apache.org/contribute/testing/] 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
(v6.3.15#6346)
