polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niclas Hedhman (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (POLYGENE-258) PolygeneTestRunner
Date Thu, 15 Jun 2017 10:37:00 GMT

     [ https://issues.apache.org/jira/browse/POLYGENE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Niclas Hedhman closed POLYGENE-258.
-----------------------------------
    Resolution: Won't Fix
      Assignee: Niclas Hedhman

TestRunners and Rules are being deprecated and only supported via adapters, and not fully,
in JUnit 5.

So let's go with the JUnit 5 Extension API instead, which is much more powerful and well-designed
than anything previously in JUnit.

> PolygeneTestRunner
> ------------------
>
>                 Key: POLYGENE-258
>                 URL: https://issues.apache.org/jira/browse/POLYGENE-258
>             Project: Polygene
>          Issue Type: New Feature
>            Reporter: Niclas Hedhman
>            Assignee: Niclas Hedhman
>             Fix For: 3.1.0
>
>
> We probably need to introduce a TestRunner for Polygene tests, to solve POLYGENE-249.
The FragmentClassLoader needs to be the one involved in loading the Polygene classes.
> It would be good to get to the point where the testcase is actually a ServiceComposite
and that the ApplicationAssembly is given as an annotation on the testcase, or better yet
a list of assemblies to be tested with the same tests.
> So, the test runner
> 1. Starts the Polygene Runtime (Energy4Java)
> 2. Takes the ApplicationAssembly from testcase annotation
> 3. Adds the testcase as a ServiceComposite to some module (which one?)
> 4. Somehow delegates the running of the methods back to Junit.
> This can become tricky, but would be pretty cool. Worst case scenario... We could make
our own Test system.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message