mendix / UnitTesting

Module to run Mendix and JUnit unit test inside a project
Apache License 2.0
7 stars 12 forks source link

Compatibility with Mx 7.10 #11

Closed Fisoes closed 6 years ago

Fisoes commented 6 years ago

Hi,

We upgrade our Mendix version from 6.10.11 to 7.10.0. Now we updated the UnitTesting module from the appstore. When we start our application it fails when it compiles Java.

Is this version not compatible with Mx 7.10?

   [javac] D:\Mendix\javasource\unittesting\RemoteApiServlet.java:20: error: package objecthandling does not exist
    [javac] import objecthandling.XPath;
    [javac]                      ^
    [javac] D:\Mendix\javasource\unittesting\TestManager.java:34: error: package objecthandling does not exist
    [javac] import objecthandling.XPath;
    [javac]                      ^
    [javac] D:\Mendix\javasource\unittesting\RemoteApiServlet.java:169: error: cannot find symbol
    [javac]             for(TestSuite suite : XPath.create(context, TestSuite.class).all()) {
    [javac]                                   ^
    [javac]   symbol:   variable XPath
    [javac]   location: class RemoteApiServlet.TestSuiteRunner
    [javac] D:\Mendix\javasource\unittesting\RemoteApiServlet.java:180: error: cannot find symbol
    [javac]             for(UnitTest test : XPath.create(context, UnitTest.class)
    [javac]                                 ^
    [javac]   symbol:   variable XPath
    [javac]   location: class RemoteApiServlet.TestSuiteRunner
    [javac] D:\Mendix\javasource\unittesting\TestManager.java:188: error: cannot find symbol
    [javac]         for(UnitTest test : XPath.create(context, UnitTest.class).eq(UnitTest.MemberNames.UnitTest_TestSuite, testSuite).all()) {
    [javac]                             ^
    [javac]   symbol:   variable XPath
    [javac]   location: class TestManager
    [javac] D:\Mendix\javasource\unittesting\TestManager.java:380: error: cannot find symbol
    [javac]             res = XPath.create(context, UnitTest.class)
    [javac]                   ^
    [javac]   symbol:   variable XPath
    [javac]   location: class TestManager
    [javac] D:\Mendix\javasource\unittesting\TestManager.java:495: error: cannot find symbol
    [javac]             TestSuite testSuite = XPath.create(context, TestSuite.class).findOrCreate(TestSuite.MemberNames.Module, module);
    [javac]                                   ^
    [javac]   symbol:   variable XPath
    [javac]   location: class TestManager
    [javac] D:\Mendix\javasource\unittesting\TestManager.java:502: error: cannot find symbol
    [javac]         XPath.create(context, TestSuite.class).not().hasReference(UnitTest.MemberNames.UnitTest_TestSuite, UnitTest.entityName).close().deleteAll();
    [javac]         ^
    [javac]   symbol:   variable XPath
    [javac]   location: class TestManager
    [javac] D:\Mendix/javasource\unittesting\TestManager.java:511: error: cannot find symbol
    [javac]             for(UnitTest test : XPath.create(context, UnitTest.class)
    [javac]                                 ^
    [javac]   symbol:   variable XPath
    [javac]   location: class TestManager
    [javac] D:\Mendix\javasource\unittesting\TestManager.java:544: error: cannot find symbol
    [javac]             for(UnitTest test : XPath.create(context, UnitTest.class)
    [javac]                                 ^
    [javac]   symbol:   variable XPath
    [javac]   location: class TestManager
    [javac] D:\Mendix\javasource\unittesting\TestManager.java:553: error: cannot find symbol
    [javac]             testSuite.setTestCount(XPath.create(context, UnitTest.class).eq(UnitTest.MemberNames.UnitTest_TestSuite, testSuite).count()); 
RoelandSalij commented 6 years ago

Hi, In mendix 7 the module makes use of the ObjectHandling module. It leaves a smaller footprint compared to Community Commons. It looks like the project is missing this module.

TimvanSteenbergen commented 6 years ago

Since most of my projects already use Community Commons, i have a question: can unittesting also use CC instead of ObjectHandling, if I want it to?

Fisoes commented 6 years ago

Thanks for the fast reply!

RoelandSalij commented 6 years ago

@TimvanSteenbergen Yes it could. However, we want to lower the footprint of the CC module by splitting it up in several modules. (Because of conflicting libraries for example)