[
https://issues.apache.org/jira/browse/TUSCANY-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531146
]
Ron Gavlin commented on TUSCANY-1817:
-------------------------------------
Hi Kelvin,
I opened this issue to raise awareness of the problem. I have some initial
design ideas but nothing real concrete at this point. A few approaches I have
thought about are:
1. Brute force approach - have existing impl tests extract their HelperContext
initialization into a template method. Then have corresponding tools-test
classes extend the impl tests and override the template method with
static-factory-based initialization.
2. More Elegant approach - Record the schemas used by each impl test somewhere.
Have a common base class be responsible for HelperContext initialization. Then
have a tools-test driver class responsible for a. iterating over impl tests, b.
performing code-generation & clean-up based on its recorded schemas, c.
code-generate a subclass of the impl test which knows how to perform static
HelperContext initialization, d. compile and invoke the code-generated test.
Any thoughts?
- Ron
> Improve SDO test infrastructure to re-use/re-execute most dynamic tests as
> static tests
> ---------------------------------------------------------------------------------------
>
> Key: TUSCANY-1817
> URL: https://issues.apache.org/jira/browse/TUSCANY-1817
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SDO Tools
> Affects Versions: Java-SDO-Next
> Reporter: Ron Gavlin
>
> Currently, static Tuscany SDO is being inadequately tested. Based on
> TUSCANY-1812, I suspect there are currently numerous dynamic test cases that
> would fail if they were executed as static test cases. I suggest the testing
> infrastructure be enhanced to allow tests to be re-used as both dynamic and
> static tests with minimal effort. The build should automatically execute
> these "shared" tests in both dynamic and static contexts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
