[
https://issues.apache.org/jira/browse/PIG-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard So updated PIG-2692:
----------------------------
Release Note:
Added the ability to mock multiple aliases when running a job.
Added assertOutputAnyOrder to be order independent.
Added user docs for mocking.
was:
Added the ability to mock multiple aliases when running a job.
Modified assertOutput to be order independent.
Status: Patch Available (was: Open)
I updated my patch. As per my previous comment, I didn't want to break
existing functionality. I added a couple assertOutputAnyOrder methods that can
be used instead of assertOutput. If you have an ordered output where it
matters use assertOutput. I managed to fix my issue with documentation and
added a section pertaining to mocking in the user docs.
> Make the Pig unit faciliities more generalizable and update javadocs
> --------------------------------------------------------------------
>
> Key: PIG-2692
> URL: https://issues.apache.org/jira/browse/PIG-2692
> Project: Pig
> Issue Type: Improvement
> Reporter: Jeremy Hanna
> Assignee: Richard So
> Priority: Minor
> Fix For: 0.15.0
>
> Attachments: pig2692.patch
>
>
> This ticket has two goals for Pig unit:
> 1) Pig unit has a really nice method assertOutput(String inputAlias, String[]
> inputValues, String outputAlias, String[] expectedOutputValues). That method
> lets you override an input alias variable with a hardcoded list of values.
> That way, the script doesn't actually have to read that input variable from
> hdfs or cassandra. Then, it runs the script and checks the specified output
> alias variable against the expected set of values. It's a really nice way to
> test your entire pig script with a single method call, but only IF your
> script has exactly 1 input and 1 output. If you want to test more
> complicated scripts, you have to jump through some hoops in order to override
> more input variables. But, it would be fairly easy to change PigUnit so that
> it can override any number of inputs and check any number of outputs and do
> so easily. That's basically the change that I put into the base testing
> class I wrote. But, it would be better to push that into PigUnit itself, and
> it's something that could easily be done in an afternoon.
> 2) Update javadocs for the pig unit test classes to make them more readable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
