Why can’t windows write @ character when selenium test runs as a service?
We have a problem with Jenkins and Selenium Grid. We are testing a web application with automated tests and have a problem with running the tests as a Jenkins job. There is a computer running as a server with Windows 10 Pro and Jenkins installed. Jenkins runs as a service so when the server restarts it is running automatically. The only problem is that when Jenkins runs as a service, somehow @ characters wont be sent to input fields. So the test wants to write an email address in an input field, but the @ character won’t be there and the test fails because of validation errors (testtest.hu). When Jenkins is started from cmd, the tests will pass, but this way, Jenkins won’t start automatically on startup. To make sure it is not a Jenkins issue I installed Selenium Grid, but the same happens. When I run it from cmd tests will pass, but when I start it from Task scheduler they will fail. I know that the difference is when these are run from a service or task scheduler they are in Session 0 isolation, but I can’t find a solution to have the tests pass in Session 0 isolation. Browser: Google Chrome in headless mode. I don’t think it is an encoding problem, because characters with accents show up in the input field.
Why can’t windows write @ character when selenium test runs as a service?
We have an automatized test framework that runs using Jenkins. The problem is when I run Jenkins as a service, we have some tests that are failing. We are testing a web application, and the test wants to write an email address ([email protected]) in an input field, but when if Jenkins runs as a service, the test won’t write the @ character and will fail because of validation errors (testtest.com). If I run Jenkins from cmd the test will pass. I tried with selenium grid, but same problem. If grid is run from cmd tests will pass. If i start grid from task scheduler, so I can have it running when the server is turned on, the test will fail. I understand that service and task scheduler commands will run is Session 0 isolated, but I don’t understand what could be different. Do you have any ideas?
I don’t think it is an encoding problem, because the test will write all characters with diacretics like éáőúöü, etc.
Browser: Google Chrome in headless mode.