[
https://issues.apache.org/jira/browse/MAPREDUCE-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769898#action_12769898
]
Philip Zeyliger commented on MAPREDUCE-1154:
--------------------------------------------
I'm vaguely uncomfortable with having a lot of code, even though it's test
code, weaved in via AspectJ. It seems like it will make it very easy to make
changes that break the testing code (because the testing code is not visible to
the regular tools, and is in an unexpected place). I understand, of course,
that the build system will check that the weaving can happen, but since these
tests are inherently large-scale and not run at every Hudson (or are they?), it
worries me a bit.
Has anyone done the "reverse" and "unweaved" functions from classes? Seems
like we could annotate functions with @RemoveInProduction, and then use some
tool to forcibly remove methods from the resulting .class files. Still opaque,
but at least it's clear where the testing code is.
If you've already been working with this in AspectJ, I'm curious how the
experience has been.
-- Philip
> Large-scale, automated test framwork for Map-Reduce
> ---------------------------------------------------
>
> Key: MAPREDUCE-1154
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1154
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: test
> Reporter: Arun C Murthy
> Fix For: 0.21.0
>
> Attachments: testing.patch
>
>
> HADOOP-6332 proposes a large-scale, automated, junit-based test-framework for
> Hadoop.
> This jira is meant to track relevant work to Map-Reduce.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
