|Re: [jakartaee-platform-dev] [EXTERNAL] Re: TCK tests in the same repo as API andSpec|
Regarding "platform tests" I'd like to move away from tests that are "owned" by the platform and instead have multi-spec integrations be "owned" by one of the specs involved.
For example, if we have a test for a BeanValidation + CDI interaction, the let the test be housed in the BeanValidation TCK. By default, when you run the BeanValidation TCK _all_ tests would run (including the BV+CDI ones), and if an implementation did not want to certify with CDI then they could explicitly disable the CDI tests by doing something like `mvn test -Dcdi=false`.
I think it will be helpful to not have tests in "no mans land" for the sake of test development and maintenance.
On Wed, Feb 26, 2020 at 8:34 AM Scott Marlow <smarlow@xxxxxxxxxx> wrote:
On Tue, Feb 25, 2020 at 6:52 PM Andy Guibert <andy.guibert@xxxxxxxxx> wrote:
> On Tue, Feb 25, 2020 at 11:35 AM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
>> In my opinion, shell script integration "doesn't count".
>> I know how to write a shell script that runs A and then runs B. That's the easy part.
>> The integration I'd like, and that we may not be able to achieve, is to only have to configure the TCK once - where is the app server, how do I deploy to it, where is the database server, where is the LDAP server, where will I find log file output, how do I configure which tests to run, etc.
> After speaking with some of the CTS experts in IBM, I would contest the claim that we currently "only have to configure the TCK once".
> All of the various configs for the TCK are in one giant (over 2.5k lines) config file:
> Additionally, each spec can also define its own config extensions like so:
> I actually see it is a drawback, rather than a benefit, that config for the entire platform TCK is in one place. For example, if I just want to run the TCKs for one spec on my company's runtime, I'd have to sift through the entire 2.5k line "common" config file and configure the parts that my spec's TCK needs.
If we include the platform level TCK tests in that one spec, then that
spec TCK will need platform level configuration, so the TCK can run
all of the platform level tests for that technology. Whether it is
one big configuration file that includes everything, or a smaller one
that includes enough configuration for running the EE server
implementation and that spec, IMO the file will likely be large anyway
because of the server settings.
jakartaee-platform-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
_______________________________________________ jakartaee-platform-dev mailing list jakartaee-platform-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!GqivPVa7Brio!LHqluJ3CA_SJnMgf4yY_EqJ_1eN0uH3BU59L4tSTO0yT8LcBffOfzvrPs4MQc7WjiQ$
Back to the top