ContributionsMost RecentMost LikesSolutionsRe: Process "crashed" and test fails when closing the application in test Just checked for clicking the "x" but that is also considered a Java Close as the Object has this alias: Aliases.javaw.ShellWorkbench. Re: Process "crashed" and test fails when closing the application in test Java Close. I also tried: go to file menu, click close application. The application is terminated (on screen at least), but when it is restarted for the next test, I end up with a message stating that the application is running (or at least its processes) if I disabled the check for running processes. So, can (and will) try the hit "X" button but I think I need to have a check (and kill) for a running process before launching the application again. Re: Process "crashed" and test fails when closing the application in test Increasing timeouts is what I've been doing and is not helping in making things more stable unfortunately. In previous incarnations of this (and similar) workbench applications they were running on Java 11. When Testcomplete closed the applications the processes were not always immediately closed or a crash popup would occur. That's why the button click was added, to click away the crash pop up and continue the test. Since the application migrated to Java 17 those popups no longer occur (hence the click OK button is now obsolete) but the process still crashes (in the background). I now changed the properties of the close application nametest to continue on error and that makes the rest of the test being finalized in good fashion. However, the end result is still marked as a failure. Any ideas how to fix that? On a side note, these popups and crashes only occur when using Testcomplete. When I do theses test manually things work fine. Re: Process "crashed" and test fails when closing the application in test Edit: found it. It is set to simple. Re: Process "crashed" and test fails when closing the application in test Here it is. The application is a Tested Application, so I could try and disable the close thing at the end to see if that helps. Re: Process "crashed" and test fails when closing the application in test Hi Robert, thanks for taking the time to read my wall of text and replying. Unfortunately, I can't agree with test 4 being the issue. Not fully yet, anyway. When I run test 4 stand alone it will crash one time, but when I re-run it, it passes without even blinking an eye. Not done enough tries to give a percentage of fails but will do so soon. IF it crashes and burns it immediately happens after I see the project being closed and the shellWorkbenchwindow receives the Close operation from Testcomplete. The close project is a separate nametest and is the last thing to fully pass before the crash occurs according to the log. Below is an example: Process "crashed" and test fails when closing the application in test Hi all, I recently migrated my Testcomplete 14 tests to 15 and am currently runningVersion: 15.49.6.7 x64. We are using Testcomplete to regression test our desktop applications and have recently upgraded our desktop application to use Java 17. The execution plan consists of several tests with the application called "Workbench". The way of working will most likely look familiar: open the "Workbench" application (to get a clean sheet) create or open a project execute the test close the project that has just been tested close the "Workbench" application next test open the "Workbench" application create or open a project execute the test close the project close the application Now, when I do a full run,let's say the execution plan has four tests to run, the following happens: Test 1 executes, the application is closed by Testcomplete andTest 2 executes, the application is closed , test 3 and 4 run but after issuing the final close "Workbench" command (after executing test 4), Testcomplete will fail the test stating the "Workbench.exe" process crashed and test execution is interrupted. However, in my opinion, the process didn't "crash" but was terminated by Testcomplete on account of the execution plan (which it did 3 times succesfully with the same nametest "CloseApplication". There are built in delays in that test to ensure the process has fully completed, but that doesn't seem to help. Any ideas? SolvedEntering text from a variable in a browser I am creating a keyword test for a desktop application in Testcomplete 14 which requires Testcomplete to authenticate to a web environment first. The login screen is a browser (splashscreen) and I let TC click the username field. I have the user id stored in a variable but I cannot get TC to enter it. I used the operation "add_TextInput" but when I run the test nothing is entered. The same happens for the password field. I can use "Keys" instead, but that means the password is visible in the keyword test, which is not acceptable. Any way how I can fix this? Re: Splitting a project to run a daytime and night time testCheers for your reply. We use Jenkins so I will talk to one of our resident Jenkins gurus to get that up and running. I think it shouldn’t be too hard to do.Splitting a project to run a daytime and night time test I am fairly new to Testcomplete and according to my co-workers, what I want should be possible, but they don't know. Here's what I want/need to do: Within my domain is a desktop application which is tested with Testcomplete. However, due to the amount of things to be tested, we want to split/clone the project in a way that a part of the tests is being done during daytime and a full(er) test is being done at night. How do I do it? - splitting/cloning the project in a day project and night project - schedule the projects to be executed at times I want them to be executed Thanks in advance! Solved