FWD » Core Development » Conversion Tools

11/25/2022

05:12 PM Feature #6237: OEUnit support

Marian Edu wrote:
> Vladimir Tsichevski wrote:
> > Seems, OE does not support multiple @ABLUnit@ life cycle unit te... Vladimir Tsichevski

09:15 AM Feature #6237: OEUnit support

Vladimir Tsichevski wrote:
> Seems, OE does not support multiple @ABLUnit@ life cycle unit test procedures, like @JU... Marian Edu

08:55 AM Feature #6237: OEUnit support

Or perhaps it makes more sense to implement the 4GL-compatible versions as annotation names which more clearly mappin... Greg Shah

08:52 AM Feature #6237: OEUnit support

> Currently FWD supports this, and I wonder whether we should do unsupport :-)
We definitely need to implement in ... Greg Shah

06:41 AM Feature #6237: OEUnit support

Vladimir Tsichevski wrote:
> Seems, OE does not support multiple @ABLUnit@ life cycle unit test procedures.
This ho... Vladimir Tsichevski

11/24/2022

11:56 AM Feature #6237: OEUnit support

Seems, OE does not support multiple @ABLUnit@ life cycle unit test procedures, like @JUnit5@ supports. That means we ... Vladimir Tsichevski

11/21/2022

01:06 PM Bug #6901 (Test): Event handling - ON ANYWHERE

Greg Shah

10:48 AM Bug #6901: Event handling - ON ANYWHERE

Greg Shah wrote:
> Hynek: Please commit the patch to 3821c.
Patch 6901.patch checked in 3821c revision 14378. Hynek Cihlar

08:24 AM Bug #6901: Event handling - ON ANYWHERE

Hynek: Please commit the patch to 3821c. Greg Shah

06:42 AM Bug #6901: Event handling - ON ANYWHERE

Marian Edu wrote:
> Hynek Cihlar wrote:
>
> > I find helpful to turn on rules tracing, this helps to pinpoint the... Marian Edu

06:36 AM Bug #6901: Event handling - ON ANYWHERE

Hynek Cihlar wrote:
> I find helpful to turn on rules tracing, this helps to pinpoint the exact place where a part... Marian Edu

06:32 AM Bug #6901: Event handling - ON ANYWHERE

Marian Edu wrote:
> It took me a while to get along understanding xml code in those rules and where/what exactly nee... Hynek Cihlar

06:17 AM Bug #6901 (Review): Event handling - ON ANYWHERE

It took me a while to get along understanding xml code in those rules and where/what exactly needs to change... this ... Marian Edu

06:15 AM Bug #6901 (WIP): Event handling - ON ANYWHERE

Marian Edu

11/18/2022

12:22 PM Feature #6237: OEUnit support

Vladimir Tsichevski wrote:
> Just found, that @@TestSuite@ annotation is not recognized and converted in procedures.... Vladimir Tsichevski

11/17/2022

02:21 PM Feature #6237: OEUnit support

Just found, that @@TestSuite@ annotation is not recognized and converted in procedures. Will fix this... Vladimir Tsichevski

11/14/2022

03:05 PM Feature #6237: OEUnit support

Greg Shah wrote:
> We need to be able to specify the bootstrap configuration path/filename for a given test run.
... Vladimir Tsichevski

01:07 PM Feature #6237: OEUnit support

The latest diff @6237-215-14360.diff@. Vladimir Tsichevski

12:56 PM Feature #6237: OEUnit support

Vladimir Tsichevski wrote:
> We should add support for the classroot selector in the engine. This selector is not us... Vladimir Tsichevski

11:39 AM Feature #6237: OEUnit support

We should add support for the classroot selector in the engine. This selector is not used by Eclipse test launcher (E... Vladimir Tsichevski

11/11/2022

04:53 PM Feature #6237: OEUnit support

Greg Shah wrote:
> We need to be able to specify the bootstrap configuration path/filename for a given test run. Di... Vladimir Tsichevski

04:40 PM Feature #6237: OEUnit support

Greg Shah wrote:
> Unpack and rethrow it in the calling code on the client.
It works!
!6237-211.png! Vladimir Tsichevski

03:20 PM Feature #6237: OEUnit support

Unpack and rethrow it in the calling code on the client. Greg Shah

02:06 PM Feature #6237: OEUnit support

Vladimir Tsichevski wrote:
> My proposal is to follow the same way, and let the assertions library, implemented in... Vladimir Tsichevski

11/09/2022

07:46 AM Feature #6237: OEUnit support

We need to be able to specify the bootstrap configuration path/filename for a given test run. Different test runs in... Greg Shah

06:41 AM Feature #6237: OEUnit support

Greg Shah wrote:
> Some questions:
>
> * How do we register our test engine with these launchers?
> ** Eclipse
... Vladimir Tsichevski

06:12 AM Feature #6237: OEUnit support

Some questions:
* How do we register our test engine with these launchers?
** Eclipse
** ant
** gradle
** JUni... Greg Shah

11/08/2022

06:06 PM Feature #6237: OEUnit support

Greg Shah wrote:
> Are you saying there is absolutely no way to ever pass configuration from some launcher to our ... Vladimir Tsichevski

04:16 PM Feature #6237: OEUnit support

> There is no such thing as "direct JUnit invocation".
I'm talking about command line launching of JUnit.
> The... Greg Shah

04:07 PM Feature #6237: OEUnit support

Greg Shah wrote:
> From #6237-61 above:
>
> I want to reuse our existing approaches to configuration (e.g. using ... Vladimir Tsichevski

02:32 PM Feature #6237: OEUnit support

From #6237-61 above:
> Gather the necessary configuration (a @BootstrapConfig@ instance) to pass to the @ClientCor... Greg Shah

01:13 PM Feature #6237: OEUnit support

I see some potential problem: the test engine has no access to the command-line parameters, since these parameters ar... Vladimir Tsichevski

12:35 PM Feature #6237: OEUnit support

The problem with referencing Java class names in test suite Java sources resolved in @6237-200-14353.diff@.
Now th... Vladimir Tsichevski

07:38 PM Feature #6237: OEUnit support

> No, I do not propose using Java exceptions instead of legacy exceptions. Instead, at the server our test engine wil... Greg Shah

11/07/2022

06:17 PM Feature #6237: OEUnit support

Greg Shah wrote:
> Although I see the value in this idea, I wonder if using the JUnit exception instead of the legac... Vladimir Tsichevski

06:00 PM Feature #6237: OEUnit support

Although I see the value in this idea, I wonder if using the JUnit exception instead of the legacy exception will hav... Greg Shah

03:38 PM Feature #6237: OEUnit support

The expected legacy exception handling implemented both in conversion and runtime.
The diff is @6237-196-14352.diff@. Vladimir Tsichevski

03:34 PM Feature #6237: OEUnit support

JUnit5 Jupiter engine uses the @org.opentest4j@ package, namely the @AssertionFailedError@ from this package to store... Vladimir Tsichevski

02:33 PM Feature #6237: OEUnit support

Problem: if the test method throws a legacy exception, it is now returned to the client, but the legacy exception is ... Vladimir Tsichevski

11/02/2022

04:43 PM Feature #6237: OEUnit support

Vladimir Tsichevski wrote:
> In @ABLUnit@ it is valid to use instance methods (no static) as "before all" and "after... Vladimir Tsichevski

01:21 PM Feature #6237: OEUnit support

In @ABLUnit@ it is valid to use instance methods (no static) as "before all" and "after all" behavior. We need to add... Vladimir Tsichevski

11/01/2022

05:01 PM Feature #6237: OEUnit support

Greg Shah wrote:
> Please fix it in our conversion (generate only one annotation and merge the data).
This is fix... Vladimir Tsichevski

03:57 PM Bug #6901: Event handling - ON ANYWHERE

There are two issues with conversion of @ON@ statement in regards to @ANYWHERE@ option found during debugging of even... Marian Edu

03:57 PM Bug #6901 (Test): Event handling - ON ANYWHERE

Marian Edu

10/31/2022

10:01 AM Feature #6237: OEUnit support

Please fix it in our conversion (generate only one annotation and merge the data). Greg Shah

10/30/2022

04:51 PM Feature #6237: OEUnit support

4gl allows multiple annotations of the same type for the same element. This is used in some customer code to implemen... Vladimir Tsichevski

10/28/2022

05:07 PM Feature #6237: OEUnit support

Issues #6237-187 (automatic disabling the engine) and #6237-186 (@@TestSuite@ support) resolved in the patch @6237-18... Vladimir Tsichevski