Usage of the temp directory for tests in JBoss testsuite

[anil.saldhana]

If a test wants to create a file that will need to be used elsewhere by the test, a possibility is to create the file in the temp folder (as obtained by System.getProperty("java.io.tmpdir")).

Are there any issues in using the tmp directory for JBoss tests? At the begin/end of the test, the files will be cleared for residual sideffect prevention.

I am not talking about a running JBoss instance being used by the testsuite, but rather the need of a standalone unit testcase for an intermediary file.

Any other options/ideas?

[brian.stansberry]

JBoss Cache has a number of unit tests that use the temp dir; most of the ones that deal with testing cache loaders. I'm not aware of this causing any problems.

[ryan.campbell]

The problem with temp files is when the tests are run on multi-user environments, you can get permission problems. This problem is reduced if you use File.deleteOnExit(). This still does not address simulatneous runs. Perhaps it would be best to use File.createTempFile() and deleteOnExit()?

[starksm64]

The problem with the creteTempFile call is that some tests need to know the names of the files. Accessing the jboss.server.temp.dir and having this availble to the test clients would allow for run local temp files that should not have any permission problems.