I know how to create a log with IntelliJ for run configurations, but is it possible to have the name of the file change dynamically each run? The documentation links to Apache Ant for patterns, but as far as I can tell, this is only used to determine which files should be watched and output to the log file.
What I would like is something like:
Save console output to file: /path/to/log/location/logForProject_${current-time}.log
Related
I am using the BDD framework using Cucumber,
There are multiple feature files.
But am not able to get the output in the HTML file. (However, I can see the output in my console. )
Where am going wrong? How to keep this file(CucmberExtentReport.html) updated in IntelliJ IDEA?
Screenshot of the folders:
Am getting the HTML output only on running the whole configuration from here
But I want to run a single feature file and see the output which IntelliJ is not updating...
I am running single feature by clicking run like this:
I am trying to create a task that needs to read from a file in IntelliJ EduTools.
I tried creating a directory at the root of the course and marked it as a resources, I tried putting the actual file in the src component of the Task. I tried a number of locations for the resource file.
Here's what I got. Once I created a resource file at the top level of the project, the task was able to work. However, the tests were not able to find the file. (I then tried creating a test resource directory in many locations without success).
Where should I place resource files for Tasks and Tests to run in IntelliJ Edu Tools?
You should put the files for tasks into the task directory and files for tests into the tests directory. Path to file should be defined like this:
./filename.extension - for task files
./tests/filename.extension - for test files
Whenever a run a unit test in Intellij (org.junit.Test), a file of the form /tmp/idea_test_*.out is produced containing some log output that looks similar to log entries that are produced by the tests but seeming with each line prefixed by "NORMAL_OUTPUT". I've grepped the codebase and it seems that neither the string "NORMAL_OUTPUT", nor the string "idea_test" is present in the repository, though I suspect some plugin or setting that I can't yet find. Does anyone have an idea what could be causing this?
I checked the log output location specified in Run/Debug Configurations > Logs > Save console output to file. This setting is not set.
These files are created by this code and are normally deleted automatically here. This is entirely part of IntelliJ IDEA's normal functioning; it is not controlled by any setting or plugin.
The location of the tmp files is governed by the JVM system property java.io.tmpdir. I found that adding this to the bin/idea.properties file had no effect on my installation, so I just edited the startup script to add the property, e.g.
-Djava.io.tmpdir=/alternative_tmp_dir
I am using JMETER for load testing. I have large number of user properties in my plan. Its not recommended to pass all these through command prompt because of size issues. I am aware that we can put all the properties in some .properties file and use that file. Like we have the user.properties file in JMETER. But I want to make my own properties file and it should be loaded after the jmeter.properties file. Can anyone guide me how I can do that.
I have gone through a link
http://www.testautomationguru.com/jmeter-property-file-reader-a-custom-config-element/
But not getting how are the following steps to be done
Download this zip file which contains a jar file.
tag-jmeter-extn-1.0.zip (784 downloads)
Go to JMETER_HOME/lib/ext foler.
Place the jar file & Restart JMeter.
Once yo launch the JMeter, You will see ‘Property File Reader’ as given below.
Thankyou
I created the plugin. Did you place the jar file in the /lib/ext folder?
If yes, then close the jmeter and launch again. Under Config Elements - you would see Property File Reader. Give the path of the property file to be read.
You can add as many Property File Reader elements as you want for each property file.
If you do not want to use any external plugin, you can simply pass the property files to the test as shown below.
jmeter -n -t test.jmx -p c/path/to/prop.properties
The main idea of using the plugin is to read the user property file during the design phase/GUI as well. Property File Reader will work in both GUI/non-GUI modes.
When I build my test I generate a server log file, which is good. The problem is that after several runs it becomes very long and it's hard to get orientate with it.
Is there any way to delete this file every run and than create it?
Have a look at the workspace cleanup plugin, with that you can add a build environment configuration to clean up specific files, in Advanced... panel you can limit deletion to certain patterns, e.g. **/*.log.
If your log file is managed outside your job's workspace, add a new build step at beginning of type Execute shell script to manually delete the log file. This works with jobs of type freestyle.