We do have 6 tests in one project. If I split those 6 tests in 6 projects without sacrificing the log ? then does it work ?
I can't say for sure because I don't know the size of your tests nor the logs that export for each one. But I would say it would definitely be worth a shot.
Finally we turn off images and the result get published to confluence.
I am looking for the options in jenkins where we can clean up the logs or reports before starting new builds
any idea ?
We have 3 testExecute VM machines . We want to run the same project in all 3 testexeute VM machines but with different datas . Using jenkins to run the project.
Do we need to maximize the Window of VM machines ? I am seeing some issue when the VM machine window is minimized and the test do not run even though we have jenkins slave agent is connected.
I am not sure how to get this. I am never able to ran the tests until I log in VMs and have the VM window should be maximized .
Attached the screenshot for setting done on Jenkins for testcomplete
Run interactive user session - Specifies whether your TestComplete test will run in an interactive session.
This option is effective only if you use TestComplete or TestExecute 10.60 or later.
If this option is disabled and Jenkins is running as a service, your TestComplete tests will fail.
For information on when you need to use this option, see Requirements.
User - The user profile that will be used to run the test.
Password - The password used to log in to the user account.
Use active session - Specifies whether an existing user session will be used to run a TestComplete test. If it is selected, TestComplete will run in the current session. Otherwise, Jenkins will close all the applications, terminate the currently active session, start a new session under the specified user account and then start the test.
|Note:||Jenkins will not stop the user session if another user is logged on.|
Session screen resolution - Select a screen resolution for the user session in which your TestComplete test will run. The default value is 1280×1024.
If you use a TestComplete version earlier than 12.30, the specified screen resolution will be ignored and the default screen resolution (1280×1024) will be used.
If the Use active session option is enabled, the specified screen resolution will be ignored and the actual screen resolution of the corresponding user session will be used.
|Note:||The maximum resolution that can be set for a user session depends on the operating system version and on the Remote Desktop Protocol version installed on the target computer. To learn more, see Remote Desktop Protocol Maximum Supported Resolutions.|
I look at the configuration link.
I am seeing the difference in launch method which is "Launch agent via java Web Start"
I am using the java Web Start launch Agent. As it has been mentioned when using the Launch Method "Let jenkins conrol this windwn slave as a window service has some other issues.
Also when I minimize the VM window I got the error - Mozilla Firefox is invisible and thus cannot be activated.
Started by user Nishchal Gupta [EnvInject] - Loading node environment variables. Building remotely on slave_plaza in workspace C:\Users\nisgupta\Documents\TestComplete\workspace\TC_UDEV_BannerFiscalGateway [TestComplete] The test execution started (Banner Fiscal Gateway/Home). [TestComplete] Found TestComplete/TestExecute installations: Type: TE, Version: 12.60.5545.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 12\bin\TestExecute.exe" [TestComplete] Selected TestComplete/TestExecute installation: Type: TE, Version: 12.60.5545.11, Path: "C:\Program Files (x86)\SmartBear\TestExecute 12\bin\TestExecute.exe" [TestComplete] [WARNING] The node is connected via Java Web Start (JNLP). In this mode, the "Run interactive user session" property of the TestComplete Test step is ignored. TestComplete (or TestExecute) will work in the current user session. [TestComplete] Launching the test runner. $ "C:\Program Files (x86)\SmartBear\TestExecute 12\bin\TestExecute.exe" "C:\Users\nisgupta\Documents\TestComplete\workspace\TC_UDEV_BannerFiscalGateway\Banner Fiscal gateway\Banner Fiscal Gateway.pjs" /run /SilentMode /ForceConversion /ns /exit /ExportLog:C:\Users\nisgupta\Documents\TestComplete\workspace\TC_UDEV_BannerFiscalGateway\7634674.tclogx /ExportLog:C:\Users\nisgupta\Documents\TestComplete\workspace\TC_UDEV_BannerFiscalGateway\7634674.htmlx /ErrorLog:C:\Users\nisgupta\Documents\TestComplete\workspace\TC_UDEV_BannerFiscalGateway\7634674.txt /ExportLog:C:\Users\nisgupta\Documents\TestComplete\workspace\TC_UDEV_BannerFiscalGateway\7634674.mht /project:Home /DoNotShowLog [TestComplete] Test runner exit code: 2. [TestComplete] [WARNING] Error: The window 'Mozilla Firefox' is invisible and thus cannot be activated.. [TestComplete] [WARNING] Errors occurred during the test execution. [TestComplete] Marking the build as UNSTABLE. [TestComplete] The test execution finished (Banner Fiscal Gateway/Home). Build step 'TestComplete Test' changed build result to UNSTABLE Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: UNSTABLE