On mac computers, you will need to allow the IDE to control their computer:
Security & Privacy
-> Accessibility
-> Allow the apps below to control your computer
and select the
IDE you are working with
Yes, please check our workflow for the UI tests example project
runIdeForUiTests {
systemProperty("jb.privacy.policy.text", "<!--999.999-->")
systemProperty("jb.consents.confirmation.enabled", "false")
}
If the commands have now been executed and a task is now started with xvfb, it will start normally and function properly!
Unfortunately, this cannot be implemented directly in Github Actions, as the commands (access on /root/...) cannot be executed. However, this can be implemented using a separate docker container. For an example, see CodeTester-IDEA.
It is important to use license file generated with offline activation code. Get your offline activation code from jba and activate it in the Idea. Find idea.key
file in configuration directory of activated ide
and copy it to a new folder and then pass this folder as configuration directory to runIdeForUiTests
task.
runIdeForUiTests {
configDirectory file('/path/to/folder')
}
Or put the idea.key
file to a default config directory build/idea-sandbox/config-uiTest
Since 2021.3 EAP version of paid ideas demand either login or license to run. For UI tests it is easier to use license:
- put license file(idea.key, clion.key...) to the config directory
build/idea-sandbox/config-uiTest
or you can specify it) - run ide with property
eap.require.license = true
runIdeForUiTests {
systemProperty "eap.require.license", "true"
}
Since 2021.1 users must trust each opened project. For UI tests it might be helpful to automatically trust test projects:
runIdeForUiTests {
systemProperty "idea.trust.all.projects", "true"
}
This project contains usage example of test recording. It uses FedericoCarboni/setup-ffmpeg
github action and com.automation-remarks:video-recorder-junit5
library with extension for JUnit5.
Check video-recorder-java for more information.