Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken test on WorkspaceCreationTest.java #41

Open
cleberjamaral opened this issue Jun 16, 2022 · 0 comments
Open

Broken test on WorkspaceCreationTest.java #41

cleberjamaral opened this issue Jun 16, 2022 · 0 comments

Comments

@cleberjamaral
Copy link
Collaborator

When the testing system is launched to test CArtAgO facilities, such as listing workspaces, get observable properties, and so on, an error is occurring when the Config.get().fix() method of src/main/java/jacamo/infra/JaCaMoLauncher.java class is performed.

Details:
The testing class calls:
TestUtils.launchSystem("src/test/java/project/p5.jcm");

It puts a JaCaMo instance in a thread and use the current thread to check when the instance is ready to perform the tests. The JaCaMo instance parses the "jcm" file and make many other default procedures to initialize the given system. The init() method calls a fix() method which is throwing an IO error:

WorkspaceCreationTest STANDARD_ERROR
    Exception in thread "Thread-3" java.lang.NullPointerException
        at java.base/java.io.File.<init>(File.java:279)
        at jacamo.util.Config.tryToFixJarFileConf(Config.java:284)
        at jacamo.util.Config.fix(Config.java:161)
        at jacamo.infra.JaCaMoLauncher.init(JaCaMoLauncher.java:113)
        at jacamo.infra.JaCaMoLauncher.main(JaCaMoLauncher.java:67)
        at jacamo.util.TestUtils$1.run(TestUtils.java:21)

Because of this error, the JaCaMo instance never get ready and the Integrated test (performed by gradle test) never finishes, printing the messages:

WorkspaceCreationTest STANDARD_OUT
    waiting for jcm to start...
    waiting for jcm to start...
    waiting for jcm to start...
    waiting for jcm to start...

I don't know why it is happening. Any thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant