[
https://issues.apache.org/jira/browse/WAVE-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ali Lown resolved WAVE-225.
---------------------------
Resolution: Not A Problem
Already as restricted as can reasonably be.
> GWT tests do not restrict permutations properly
> -----------------------------------------------
>
> Key: WAVE-225
> URL: https://issues.apache.org/jira/browse/WAVE-225
> Project: Wave
> Issue Type: Bug
> Priority: Minor
>
> <b>What steps will reproduce the problem?</b>
> 1. Run a gwt test.
> <b>What is the expected output? What do you see instead?</b>
> Expected output is something within a few minutes. Instead, it takes way too
> long, and even a trivial test can timeout due to the large number of default
> permutations that are being frivolously compiled.
> The only permutations that should be used for GWT tests, if any, are
> user-agent permutations. It's just not practical to have any more than that.
> My suggestion is to be simple, and make all test modules declare explicitly
> the exact number of permutations in which it should run, by inheriting from
> restrictors that should be littered around a few top-level packages (e.g.,
> OnePermutation.gwt.xml and AllPermutations.gwt.xml). The default should
> always be OnePermutation.
> Of course, nothing can enforce anything about the number of permutations that
> are used for a test, because of the brittleness and non-locality of how
> restrictions work with module definitions, but it should be an improvement.
> ---
> Issue imported from
> http://code.google.com/p/wave-protocol/issues/detail?id=226
> Owner: [email protected]
> Label: Type-Defect
> Label: Priority-Medium
> Stars: 1
> State: open
> Status: Accepted
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
