Fix bug for multiple returned values

[scott-gunn]

Fixed a bug where only the first value was being computed, and refactored the unit test into its own section as it should have been done originally.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[akalotkin]

@scott-gunn, I think we should add unit test that covers the issue.

[scott-gunn]

@scott-gunn, I think we should add unit test that covers the issue.

Deequ unit tests aren't built to handle this case, each test just unit tests the individual metric for a single value. They don't go through a runtime that spits out multiple values. I am going to add a unit test to our in-house mdl-dqa project though as it can handle it since it runs through the runAnomalyChecks function which looks like it will hit this bug.

[akalotkin]

@scott-gunn, I think we should add unit test that covers the issue.

Deequ unit tests aren't built to handle this case, each test just unit tests the individual metric for a single value. They don't go through a runtime that spits out multiple values. I am going to add a unit test to our in-house mdl-dqa project though as it can handle it since it runs through the runAnomalyChecks function which looks like it will hit this bug.

I think it should be possible to add multiple analyzers to a single test. Like here:

deequ/src/test/scala/com/amazon/deequ/analyzers/AnalysisTest.scala

Line 240 in 101142e

"return the proper exception when the number of max histogram bins is too big" in