Resource files not found from JUnit test cases

Question

Summary  My JUnit tests are not finding the files they require during execution  I m using Maven for dependency management and compilation   Details  All files required by the test cases are located in  src test resources   For example  src test resources resourceFile txt   To access a resource I use the following code   URL url   getClass   getResource   resourceFile txt   getFile    File file   new File url     But then file exists   returns false  And the error I get is   Tests in error     myJUnitTestCase tests MyJUnitTestClass    home me workspace Project 20Name target test-classes resourceFile txt  No such file or directory    Note  the following gives the same error  notice the removed   prefix    URL url   getClass   getClassLoader   getResource  resourceFile txt   getFile    File file   new File url     It seems as though the files from src test resources are not getting copied into target test-classes   Any ideas   The following questions did not help  Why Can  39 t I access src test resources in Junit test run with Maven   Loading Properties File In JUnit  BeforeClass  How to deal with the test data in Junit   Software Versions  Ubuntu 12 04   Apache Maven 2 2 1  Java 1 7 0  Eclipse  Java EE IDE for Web Developers  Indigo Service Release 2   truncated  Maven POM   lt  xml version  1 0  encoding  UTF-8   gt   lt project gt       lt modelVersion gt 4 0 0 lt  modelVersion gt       lt groupId gt com groupId lt  groupId gt       lt artifactId gt artifactId lt  artifactId gt       lt packaging gt jar lt  packaging gt       lt version gt 1 0-SNAPSHOT lt  version gt       lt name gt name lt  name gt       lt build gt           lt finalName gt name lt  finalName gt           lt directory gt target lt  directory gt           lt outputDirectory gt target classes lt  outputDirectory gt           lt testOutputDirectory gt target test-classes lt  testOutputDirectory gt           lt sourceDirectory gt src main java lt  sourceDirectory gt           lt testSourceDirectory gt src test java lt  testSourceDirectory gt           lt resources gt               lt resource gt                   lt directory gt src main resources lt  directory gt               lt  resource gt           lt  resources gt           lt testResources gt               lt testResource gt                   lt directory gt src test resources lt  directory gt               lt  testResource gt           lt  testResources gt           lt plugins gt               lt plugin gt                   lt groupId gt org apache maven plugins lt  groupId gt                   lt artifactId gt maven-compiler-plugin lt  artifactId gt                   lt configuration gt                       lt source gt 1 6 lt  source gt                       lt target gt 1 6 lt  target gt                       lt encoding gt UTF-8 lt  encoding gt                   lt  configuration gt               lt  plugin gt           lt  plugins gt       lt  build gt       lt dependencies gt           lt dependency gt               lt groupId gt junit lt  groupId gt               lt artifactId gt junit lt  artifactId gt               lt version gt 4 10 lt  version gt               lt scope gt test lt  scope gt           lt  dependency gt       lt  dependencies gt   lt  project gt

User · Answer

This is actually redundant except in cases where you want to override the defaults. All of these settings are implied defaults.

You can verify that by checking your effective POM using this command

mvn help:effective-pom

    <finalName>name</finalName>
    <directory>target</directory>
    <outputDirectory>target/classes</outputDirectory>
    <testOutputDirectory>target/test-classes</testOutputDirectory>
    <sourceDirectory>src/main/java</sourceDirectory>
    <testSourceDirectory>src/test/java</testSourceDirectory>
    <resources>
        <resource>
            <directory>src/main/resources</directory>
        </resource>
    </resources>
    <testResources>
        <testResource>
            <directory>src/test/resources</directory>
        </testResource>
    </testResources>

For example, if i want to point to a different test resource path or resource path you should use this otherwise you don't.

    <resources>
        <resource>
            <directory>/home/josh/desktop/app_resources</directory>
        </resource>
    </resources>
    <testResources>
        <testResource>
            <directory>/home/josh/desktop/test_resources</directory>
        </testResource>
    </testResources>

User · Answer

You know that Maven is based on the Convention over Configuration pardigm  so you shouldn t configure things which are the defaults   All that stuff represents the default in Maven  So best practice is don t define it it s already done        lt directory gt target lt  directory gt       lt outputDirectory gt target classes lt  outputDirectory gt       lt testOutputDirectory gt target test-classes lt  testOutputDirectory gt       lt sourceDirectory gt src main java lt  sourceDirectory gt       lt testSourceDirectory gt src test java lt  testSourceDirectory gt       lt resources gt           lt resource gt               lt directory gt src main resources lt  directory gt           lt  resource gt       lt  resources gt       lt testResources gt           lt testResource gt               lt directory gt src test resources lt  directory gt           lt  testResource gt       lt  testResources gt

User · Answer

Make  maven test skip  as false in pom file  while building project test reource will come under test-classes   lt maven test skip gt false lt  maven test skip gt

User · Answer

Main classes should be under src main java  and   test classes should be under src test java   If all in the correct places and still main classes are not accessible then Right click project    Maven    Update Project  Hope so this will resolve the issue

User · Answer

My mistake  the resource files WERE actually copied to target test-classes  The problem seemed to be due to spaces in my project name  e g  Project 20Name   I m now loading the file as follows and it works   org apache commons io FileUtils toFile myClass   getResource  resourceFile txt         Or   taken from Java  how to get a File from an escaped URL   this may be better  no dependency on Apache Commons    myClass   getResource  resourceFile txt     toURI

User · Answer

The test Resource files src test resources  are loaded to target test-classes sub folder  So we can use the below code to load the test resource files   String resource    sample txt   File file   new File getClass   getClassLoader   getResource resource  getFile      System out println file getAbsolutePath       Note    Here the sample txt file should be placed under src test resources folder   For more details refer options to load test resources

[java] Resource files not found from JUnit test cases

Examples related to java

Examples related to unit-testing

Examples related to maven

Examples related to junit

Examples related to resourcebundle