GitHub user bjchambers opened a pull request:

    https://github.com/apache/beam/pull/3537

    TestPipeline should support errors in expand

    Writing a test that expects an exception during transform application is
    currently not possible with TestPipeline in a NeedsRunner or
    ValidatesRunner test. The exception causes the pipeline to be unrunnable.
    
    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
    
     - [*] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [*] Make sure tests pass via `mvn clean verify`.
     - [*] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [*] If this contribution is large, please file an Apache
           [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf).
    
    ---


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bjchambers/beam 
test-pipeline-construction-errors

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/beam/pull/3537.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3537
    
----
commit 5d820c690540322f2d3c5869061703b8e460069f
Author: bchambers <bchamb...@google.com>
Date:   2017-07-11T00:29:24Z

    TestPipeline should support errors in expand
    
    Writing a test that expects an exception during transform application is
    currently not possible with TestPipeline in a NeedsRunner or
    ValidatesRunner test. The exception causes the pipeline to be unrunnable.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to