[
https://issues.jboss.org/browse/ARQ-1994?page=com.atlassian.jira.plugin.s...
]
Aslak Knutsen commented on ARQ-1994:
------------------------------------
This is not a bug. This is the effect of in-container testing. If you run in-container the
test code is executed inside the server not inside your 'IDE'.
You have 2 options;
1. You really wanted to run the test on the client side and only reach the deployment via
external exported endpoints, e.g. http, then you can use @Deployment.testable=false.
2. Or you want to test in-container but require resources only available on the client
side. Then add those resources to the Deployment and load them via the Classloader, not
file system.
Wrong root path in Testcase
---------------------------
Key: ARQ-1994
URL:
https://issues.jboss.org/browse/ARQ-1994
Project: Arquillian
Issue Type: Bug
Affects Versions: 1.1.8.Final, 1.1.9.Final
Reporter: pueffl
After deploying a .war to JBoss Wildfly, I start a Testcase and want to read a XML-File
from the filesystem (relative path -> <Project>/target/test-classes). As this
didn't work, I checked the path: System.out.println(new
File("test.txt").getAbsolutePath());
The result was <WILDFLY-HOME/bin/test.txt which was really a big surprise! :-)
I am not absolutely sure if this is a bug, but it hampers testing a lot in some cases and
it should at least be better documented. (I couldn't find information about this
behavior so far.)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)