Re: [jakartabatch-dev] TCK directions / form factor , e.g. Arquillian -

["Scott Kurz" <skurz@xxxxxxxxxx>]

Cheng,

You'll see my (lengthy) response I just sent. on this thread. don't want to ignore your point though.

I agree that for someone new to batch, I would hate to have them have to learn Arquillian to do so, and I feel like the sample projects you mentioned are good starting points.

But for someone willing to help on the TCK or on Jakarta, well, automating the execution against different app servers is a fundamental aspect of the TCK, so I think the gains in abstracting deployment would be worth it.

I would like us, as a project, to have a few POMs and arquillian.xml(s), one for each active batch implementation, so anyone can validate any impl against any test easily. I think that's worth the complication of Arq or a similar framework, whatever we decide on.

Thanks, and please see what you think about the other thread,
------------------------------------------------------
Scott Kurz
WebSphere Batch and Developer Experience
skurz@xxxxxxxxxx
--------------------------------------------------------

Cheng Fang ---03/18/2020 11:04:37 AM---Just to add my 2 cents (late to this discussion as I just subscribed). I prefer not to add Arquillia

From: Cheng Fang <cfang@xxxxxxxxxx>
To: jakartabatch-dev@xxxxxxxxxxx
Date: 03/18/2020 11:04 AM
Subject: [EXTERNAL] Re: [jakartabatch-dev] TCK directions / form factor , e.g. Arquillian - opinions wanted
Sent by: jakartabatch-dev-bounces@xxxxxxxxxxx

---

Just to add my 2 cents (late to this discussion as I just subscribed). I prefer not to add Arquillian to the TCK.  It would add unnecessary dependency and burden with limited gains.

For developers new to batch, it adds extra barriers to force them to learn Arq annotations and api. To help them try out new tests, I think the best way is to provide some hello-world style sample batch app (in both standalone, and EE apps), so that they can quickly add a few lines and get running. This is what we have been doing in project jberet with jberet-simple, numbers-chunk & jberet-wildfly-samples.

Adding Arq makes batch app specific to the running environment, and makes it hard to share the app with others who are not using or not familiar with Arq.  We all spend a huge amount of time debugging tests and running apps, probably more than the time spent on writing apps and tests. Arq is yet another variable when it comes to debugging with its own annotation, api, configuration and other quirks.  Arq does help with developer productivity when writing tests, but that will be offsetted when comes debugging time.

Cheng_______________________________________________
jakartabatch-dev mailing list
jakartabatch-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartabatch-dev