I think my issue may be that I'm using a parameterized unit test that is a
JenkinsRule test. I suspect the parallel may not operate with tests with
parameters defined at run time and using a non-default RunWith.
I generally prefer to only use JenkinsRule tests when I can't avoid them,
because
Parallelization operates at the granularity of suites, not cases.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I'd attempted various experiments with parallel execution of tests for the
git client plugin (particularly the credentials tests which tend to be slow
and spend much of their time transferring data from external git
repositories). I never found settings that improved performance over the
defaults
Hi noble Jenkins developers,
I am wondering how to make my unit tests (well, they're integration ones in
reality, aren't they), based on Jenkins Unit test harness, faster.
I have like 35 tests, and it takes approximately 9 minutes to execute them.
I want to reduce this time. I use the default
On Thu, Nov 12, 2015 at 10:07 AM, Kirill wrote:
> I have like 35 tests, and it takes approximately 9 minutes to execute them.
> I want to reduce this time. I use the default Surefire settings, and if I
> try to play around with forking options like advised on Surefire page
The