Taher Alkhateeb writes:
> I keep forgetting this project carries a lot of history with it. Maybe
> it's because I'm a relatively new. Thank you for sharing Scott, quite
> informative.
Same here.
> If the main advantage is parallelization but that was not really used,
> then maybe it's not
I keep forgetting this project carries a lot of history with it. Maybe
it's because I'm a relatively new. Thank you for sharing Scott, quite
informative.
If the main advantage is parallelization but that was not really used,
then maybe it's not super necessary. Maybe one way to think about this
The use of separate individual dispatchers/delegators per test suite was
introduced at the same time as the delegator rollback/reset code, and was
intended to allow for test suites to be run (and data to be reset) in
parallel.
The test framework never sees much love though so that never happened.
Ahh, Now I understand what you mean by looking at your patch. I
recommend next time that you copy-paste into the email thread because
people who try to access this thread using the ML archives might not
see your attachments.
At a first glance, although this feature is not used in the current
Here is what I precisely want to remove.
>From 66150cc98d2b7b84ee5aa4dee1e25f60556577e6 Mon Sep 17 00:00:00 2001
From: Mathieu Lirzin
Date: Sun, 21 Oct 2018 16:02:38 +0200
Subject: [PATCH] Disallow using alternate dispatcher and delegator for
integration tests
---
framework/testtools
An example could shed some light here perhaps? What do you want to
remove from where? How is it complex?
On Sun, Oct 21, 2018 at 5:17 PM Mathieu Lirzin
wrote:
>
> Hello,
>
> I am trying to simplify the way integration tests are currently run.
> While looking at
Hello,
I am trying to simplify the way integration tests are currently run.
While looking at ‘org.apache.ofbiz.testtools.ModelTestSuite’ I have
found that it is possible to define alternate dispatcher and delegator
for specific tests.
This feature is not used anywhere in the framework and
