Directory structure is not preserved when copying test files to the build directory
See original GitHub issueIn our src/test/jmeter
directory we have a structure like the following:
src/test/jmeter
├── MyTestSuite.jmx
├── MyTestSuiteResources
└── resource.csv
Since 2.x when running the tests through the plugin, files from the test directory are copied by ignoring sub-directories. So the files end up in a flat structure:
target/jmeter/testFiles
├── MyTestSuite.jmx
└── MyTestSuiteResources_resource.csv
That’s a problem since our tests are referring to the resource files using a relative path and thus the file can’t be found when running the tests.
Issue Analytics
- State:
- Created 7 years ago
- Comments:19 (9 by maintainers)
Top Results From Across the Web
Copying build output files, preserving directory structure, gives ...
With these changes, it appears to work just like I want it to: files are copied to the intended target directory, and the...
Read more >Preserve the directory structure when copying - MSDN
Hi All,. This is my scenario: I have a source folder and destination folder, plz see below image for details: When i copy...
Read more >How to copy files while keeping directory structure?
The command will put every directory path with the name test into the variable TESTDIRS . ... More elegant solution (this one moves...
Read more >How to copy file preserving directory path in Linux?
First use mkdir -p to create the destination folder with recursive parent path creation. Then copy the contents to the destination folder:
Read more >The Ultimate Guide to Copying Files and Folders Using Xcopy
Creates a recursive folder structure at the destination without copying the files. This option does not include copying empty folders. To ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
At the moment I haven;t really had time to investigate it. When i get a free moment I will have a look and try and work out what to do.
It should have been but we were not copying files across to the target directory (something you should be doing).
Basically we fixed a bug where we were running the source files rather than copying the source files across to the target directory to then run them.