Aquileo | Recent changes to support-requests

Aquileo | #4 move to GitHub?

Sat, 17 Oct 2015 12:22:08 -0000

Hi Alchemist,

I suppose I should be ashamed: 1 month for a 5 minutes operation... but here it is: https://github.com/MoreUnit/MoreUnit-Eclipse!

The code has been hidden on SourceForge, but issues can be submitted both on SourceForge and Github for now.

Aquileo | #4 move to GitHub?

Mon, 14 Sep 2015 03:10:25 -0000

@ndemengel: I forgot to mention: I'm willing to volunteer to take over maintenance of the code and to respond to PRs.

Aquileo | #4 move to GitHub?

Sun, 13 Sep 2015 07:18:46 -0000

Hi Alchemist,

We never really felt the need for it in the past, but I agree that it would totally make sense now that we - the 2 developers - are far less available for the project. A move to Github would allow for easy forks and pull requests from users. There's no need to move the website, the code would suffice.

@gianasista: what do you think about it?

Aquileo | move to GitHub?

Fri, 04 Sep 2015 15:51:29 -0000

Could we move to GitHub? I was surprised that https://github.com/MoreUnit only has the IntelliJ plugin.

Aquileo | #3 request for JMockit test creation to add @RunWith(JMockit.class)

Wed, 21 Jan 2015 20:04:26 -0000

status: open --> closed
assigned_to: Nicolas Demengel

Aquileo | #3 request for JMockit test creation to add @RunWith(JMockit.class)

Wed, 21 Jan 2015 20:03:22 -0000

Ready to ship: @RunWith(JMockit.class) is now the default.

Aquileo | #3 request for JMockit test creation to add @RunWith(JMockit.class)

Fri, 22 Aug 2014 13:31:44 -0000

No problem, thanks for the great piece of software!

Aquileo | #3 request for JMockit test creation to add @RunWith(JMockit.class)

Fri, 22 Aug 2014 07:12:18 -0000

Conversely, users used to the current behavior might be surprised!

That said, given the magic needed for JMockit to work without @RunWith, it's likely better to follow your advice and make it the default, with another profile called "Without JUnit's @RunWith" for people liking the current behavior.

Many thanks for your help!

Aquileo | #3 request for JMockit test creation to add @RunWith(JMockit.class)

Thu, 21 Aug 2014 13:32:04 -0000

@Nicolas: I tested it by running MoreUnit as an Eclipse application (Run As -> Eclipse Application/PlugIn; I forget which one exactly).

Thanks for including it!

May I suggest making it the default if "JMockit" is selected? Otherwise, it might not work properly and people might blame MoreUnit. :(

Aquileo | #3 request for JMockit test creation to add @RunWith(JMockit.class)

Mon, 18 Aug 2014 11:49:22 -0000

Hi Alchemist,

I finally had a look at your template: it works perfectly for me. That said, I don't know how you tested it: did you build MoreUnit with that change, or did you put the template in your <workspace>/.metadata/.plugins/org.moreunit.mock/templates directory ? In the later case, be sure to give the template a different id, or it will be rejected (normally with an error in a popup window).

It should work if you put a .xml file in the previously mentioned directory, with the following content :
<?xml version="1.0" encoding="UTF-8" ?>

<mocking-templates version="1.0">
    <category id="org.moreunit.mock.jmockit" name="JMockit"/>
    <mocking-template
        id="org.moreunit.mock.jmockitUsingJunitRunWith"
        category="org.moreunit.mock.jmockit"
        name="Using JUnit's @RunWith">
        <code-template id="jmockitRunnerDeclaration" part="test-class-annotation">
            <include-if condition="test-type" value="junit4"/>
            <pattern><![CDATA[@${runWith:newType(org.junit.runner.RunWith)}(${runner:newType(mockit.integration.junit4.JMockit)}.class)]]></pattern>
        </code-template>
        <code-template id="dependencyDeclaration" part="test-class-fields">
            <pattern><![CDATA[

                @${injectableAnnotation:newType(mockit.Injectable)} private ${dependencyType} ${dependency};
            ]]></pattern>
        </code-template>
        <code-template id="objectUnderTestDeclaration" part="test-class-fields">
            <pattern><![CDATA[

                @${mockAnnotation:newType(mockit.Tested)} private ${objectUnderTestType} ${objectUnderTest};
            ]]></pattern>
        </code-template>
    </mocking-template>
</mocking-templates>

You can then either restart Eclipse or click on Preferences > MoreUnit > Java > Mock Generation > Reload templates, and then choose the template JMockit > Using JUnit's @RunWith

Also, I will include your template in the next version of MoreUnit, as another JMockit template named "Using JUnit's @RunWith", in order to let the default template aligned with what seems to be JMockit's default way of configuring it.

As an aside: unfortunately we have been very bad at answering MoreUnit's users for one year... I shall be more available now, at the very least until mid-September, so don't hesitate to ask for more help if needed.

Nicolas