karate.write() writes to the wrong project about intellij-plugin HOT 7 CLOSED

@arnaldop we are investigating this, the implementation within karate is blindly using ./target or ./build depending on whether gradle was detected in the invoking cli command.

I wonder if there is a setting to change the "working directory" in an intellij run-configuration

from intellij-plugin.

@ptrthomas, there seems to be, and it worked great!!!

I also added it to the Karate Feature configuration template, so that new Karate Features should benefit from this automatically. But it would be nice if $MODULE_WORKING_DIR$ was the default if the Working Directory field is empty.

from intellij-plugin.

@arnaldop great !

from intellij-plugin.

I don't believe this ticket should be closed.
The plugin should have a deterministic behavior for its default.
What I mentioned above is a workaround.
Possible solutions:

1. As mentioned above, if the working directory is not provided, it should assume the working directory of the Karate module.
2. Configure the plugin so that the default template settings include $MODULE_WORKING_DIR$ for the working directory.
   Either way, the current behavior is non-intuitive, non-deterministic, and hard to explain/define.
   Thanks.

from intellij-plugin.

Sorry, the reason for closing it wasn‘t clear. This is fixed for the next update by defaulting to the module working dir for newly created run configurations. There‘s no change of behavior for existing run configurations, so far.

from intellij-plugin.

@ptrthomas, this came back up as a problem again. Same exact behavior. The only issue is that the updated plugin does not have a way to define the Working Directory...

This failed: -Duser.dir=$MODULE_WORKING_DIR$
This hung on the write: -Duser.dir=/Users/arnaldopiccinelli/dev/projectDir/testing

from intellij-plugin.

thanks @arnaldop opened #51 to track this for the new plugin

from intellij-plugin.