While running the ROBOT Framework scripts (GUI tests) in Headless Chrome, execution taking long time.
For Wait until element visible, in debug file, POST command is returning 200 and stuck. Not moving to next step, nor failing the script.
I need to terminate the execution.
Any way to overcome this problem? Thanks.
Version details:
Python - 3.8.5, RF - 3.22, RF Selenium - 4.5, Selenium - 3.141
Try to update Selenium library, latest version is 5.1.3.
pip install --upgrade robotframework-seleniumlibrary
Update your browser and browser driver then give a try.
Related
System: M1 mac with 16G of memory, OS Ventura.
My large application with codelite builds fine with g++ and comes up and runs. There are features that don't work correctly, so I need a debugger. When I try to start either lldb or gdg either something flashes on the monitor and stops or simply just does nothing. Codelite has worked well for me for 13 years. I hope someone has a similar problem. My only choice now is to use lldb from the command line, and this is difficult for me.
I changed debuggers frequently tried to acquire an older version of codelite, asked for help on ther codelite forums and got no response.
CodeLite no longer supports lldb directly (on all platforms).
It has moved to use the new DAP (Debug Adapter Protocol) method of debugging code.
On macOS, you should install lldb-vscode via brew:
brew install llvm
In CodeLite make sure that the DebugAdapterClient plugin is loaded: Plugins -> Manage...
Force a new scan: Settings -> Debug Adapter Client and CodeLite should detect the new debugger
In your project, change the debugger to lldb-vscode
You can read more about DAP integration here:
https://docs.codelite.org/plugins/dap/
Using: VS Code
Working on: Running automation test scripts for WebdriverIO.
Error facing:
because of this error, my test specs are not executing. Is there any way to get rid of this??
Please follow the below steps to resolve this issue
Uninstall the current version of node.js.
Go to https://nodejs.org/en/blog/release/
Install the previous version of node.js (I installed from here 4.
https://nodejs.org/dist/v14.17.3/node-v14.17.3-x64.msi)
Restart your system
Try building the project using npm install
I hope this will solve your problem
The error here is coming from the Fibers npm package. Fibers only supports node versions before version 16. I had the same error message and switched the node version to 14.20.0 ,which is the newest LTS before version before 16 at the moment, and that solved the problem for me.
In our pipeline for the past 3 weeks, the dotnet test task has not been terminating at all, and we are forced to cancel the pipeline.
We have observed this log, which we had not seen prior to 3 weeks: (No changes have been made in these 3 weeks at all, either to our code or to Windows on our on premise agent, SQL Server or any other service in the agent).
The STDIO streams did not close within 10 seconds of the exit event from process 'C:\AzAgent_work_tool\dotnet\dotnet.exe'. This may indicate a child process inherited the STDIO streams and has not yet exited.
##[error]Error: The process 'C:\AzAgent_work_tool\dotnet\dotnet.exe' failed with exit code 1
All the tests in the task pass though.
Publishing test results to test run '1033120'.
TestResults To Publish 233, Test run id:1033120
Test results publishing 233, remaining: 0. Test run id: 1033120
Published Test Run :
The test results are published.
We have observed this in the logs:
*##[warning].NET 5 has some compatibility issues with older Nuget versions(<=5.7), so if you are using an older Nuget version(and not dotnet cli) to restore, then the dotnet cli commands (e.g. dotnet build) which rely on such restored packages might fail. To mitigate such error, you can either: (1) - Use dotnet cli to restore, (2) - Use Nuget version 5.8 to restore, (3) - Use global.json using an older sdk version(<=3) to build
Info: Azure Pipelines hosted agents have been updated and now contain .Net 5.x SDK/Runtime along with the older .Net Core version which are currently lts. Unless you have locked down a SDK version for your project(s), 5.x SDK might be picked up which might have breaking behavior as compared to previous versions. You can learn more about the breaking changes here: https://learn.microsoft.com/en-us/dotnet/core/tools/ and https://learn.microsoft.com/en-us/dotnet/core/compatibility/ . To learn about more such changes and troubleshoot, refer here: https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/build/dotnet-core-cli?view=azure-devops#troubleshooting*
Hence we added this in our yaml before the test task, as our app is built with .NET Core 3.1:
- task: UseDotNet#2
inputs:
packageType: sdk
version: 3.x
installationPath: $(Agent.ToolsDirectory)/dotnet
displayName: 'Installing .net core sdk 3.x'
condition: succeeded()
I did a little investigation and found this link on the MS github page: https://github.com/microsoft/azure-pipelines-tasks/issues/13033
We have set these variables: TASKLIB_TEST_TOOLRUNNER_EXITDELAY 60000
name: 'NUGET_PLUGIN_REQUEST_TIMEOUT_IN_SECONDS'
value: 30
name: 'NUGET_PLUGIN_HANDSHAKE_TIMEOUT_IN_SECONDS'
value: 30
No effect yet. How can we solve this issue? It is not affecting our release but we would like to have a green pipeline? Tips on this would be greatly helpful
Thanks for Ashwin's answer.
There was an issue with chromedriver exe which used was not updated for chrome 89. Hence one of the tests was hanging. So then after changing the chromedriver and removing the filter, the tests ran fine and the stage terminated. So no changes to pipeline yaml were required.
Posting here so others who have the same issue can find this answer quickly.
Wondered if someone could help. Just started using protractor to automate our tests. These were working fine but now when chrome is launching it closes straight away. I've been told my webdriver needs updating but I can't seem to get it to go past version 2.22. When doing new webdriver-manager update it still goes to the older version. Also been to the website to get the zip file but no matter where I put it I can't get it up update.
This is for a mac machine. Any tips would be appreciated. When I go to localhost:4444/wd/hub', when the web driver has been started and click start session it fails. This has only started since chrome updated to version 54.
You need to update your webdriver-manager (chromedriver to 2.24), but as i observed, 'webdriver-manager update' command is not updatinng chromedriver to 2.24, so the workaround is just remove the protractor and webdriver-manager from your system and install it again.
To remove webdriver-manager and protractor from global:
just delete folders from 'C:\Users\YOUR_USER_NAME\AppData\Roaming\npm\node_modules'
And install it again by using:
'npm install -g webdriver-manager',
'npm install -g protractor'
I have the latest PhpStorm (2016.2) and PHPUnit phar (5.5.4). For some reason when I run a PHPUnit test in my project in PhpStorm, it is adding on --teamcity to the run command, resulting in a failure:
Testing started at 12:52 PM ...
Unit test suite invoked with a path to a non-unit test: --teamcity
Process finished with exit code 1
I have no idea where this --teamcity option is coming from, it happens no matter what test I run, and even when starting from a blank configuration. I also do NOT have the TeamCity plugin installed, I don't even use TeamCity.
Here's what the full command appears as:
/usr/local/Cellar/php70/7.0.9/bin/php /Users/name/bin/phpunit-5.5.4.phar --configuration /path/to/config/my-phpunit.xml ClassNameTest /Users/name/PhpstormProjects/path/to/tests/unit/app/ClassNameTest.php --teamcity
(sensitive information swapped out)
All I want to do is get rid of this --teamcity option, everything works if I run in a separate terminal window without that option. This only recently started happening, maybe after a PhpStorm update.
tl;dr
I only could resolve this by removing the system installed phpunit instance from my system (Linux):
sudo apt remove phpunit-*
Details
Even if the setting in PhpStorm was to use composer autoloader:
for some reason it ended up using TeamCity from /usr/share/php/PHPUnit/Util/Log/TeamCity.php:
Project's local PHPUnit was 6.2 while the system default was 5.1 -> they're incompatible.
I spent half a day struggling with this. The underlying issue is switching between PHPUnit versions (6.x.x -> 4.x.x). (Happened to me by switching branches)
A click on the refresh button in the PHPUnit preferences fixes it.
(Languages & Frameworks > PHP > PHPUnit)
Make sure the version of PHPUnit it thinks you have matches the one it reports.
This --teamcity option is used by PHPStorm to output tests result.
What you're facing is an issue caused by PHP7 and an old version of PHPUnit.
Remove your PHPUnit 5 and install the latest one (currently 6.2) with composer and use PHPUnit namespaces instead.
More info on this bug: https://github.com/sebastianbergmann/phpunit/issues/2460
Problem was internal to the project. PHPUnit does not contain that error message. Sorry!