1

I'm very new to App-V, which is evaluated in my office. I have a Selenium test suite written in JUnit5 and can launch it as gradle test task using gradle-wrapper. My final goal is to run this on App-V5.1 virtualized environment, similar as this question.

As followed the link which was mentioned the answer, I tried to launch cmd.exe within the App-V environment, and it seeded works. Then, I tried to do this:

./gradlew --no-daemon clean test

Then the testClasses phase works perfectly, but in the test phase, I got an error like:

Could not write standard input into: Gradle Worker 1.
java.io.IOException: The pipe is being closed
   ...

(Sorry I couldn't show you the actual error log due to security reason, but it is similar to this question.)

May I wrong something? What's the right way to launch a gradle test in App-V env?

Naruhiko Ogasawara
  • 21
  • 2

1 Answers1

0

Have you tried launching cmd.exe from within the virtual bubble? I find the best way to do this is to create a shortcut to cmd.exe during sequencing and use this to troubleshoot.

If your process works within the bubble, the solution may be as simple as allowing Local Interaction. Have a read here about that.

SolidSid
  • 319
  • 1
  • 10
  • Yes, I have tried it, running cmd.exe (and gradle tasks as a subprocess) within the virtual bubble, by creating shortcut with `/appvve:` option. I'll check the doc you mentioned, thanks! – Naruhiko Ogasawara Mar 08 '19 at 23:39
  • Did the gardle task work in these conditions? If so, this will indicate where the problem is. A further question, did you run the gardle task during sequencing and did it work then? – SolidSid Mar 11 '19 at 08:22