Install macos ventura not responding9/6/2023 ![]() POST /v1:GetModels?key=AIzaSyBOti4mM-6x9WDnZIjIeyEU21OpBXqWBgw 200 586.587 ms. GET /v1/pages/ChRDaHJvbWUvMTA4LjAuNTM1OS45OBIQCUuvX4XcrqZJEgUNN5ze0w=?alt=proto 200 519.985 ms. GET /v1/pages/ChRDaHJvbWUvMTA4LjAuNTM1OS45OBIQCZn9u06bB-cGEgUNE1Cf1A=?alt=proto 200 615.048 ms. GET /_cypress/runner/cypress_runner.js 200 1.653 ms. POST /ListAccounts?gpsia=1&source=ChromiumBrowser&json=standard 200 618.486 ms. ![]() GET /chrome-variations/seed?osname=mac&channel=stable&milestone=108 304 618.895 ms. GET /_cypress/runner/cypress_runner.css 200 1.483 ms. Hot Module Replacement (HMR) is not enabled! React Refresh requires HMR to function properly. Loopback: Content not from webpack is served from '/Users/matthew/workspace/electra-web/investment-manager-control-ui/app/public' directory Proxy created: /api,/auth,/signin-oidc,/signout-callback-oidc -> Project is running at: tsconfig-paths will be removing HtmlWebpackPlugin from removing HotModuleReplacementPlugin from configuration. Cypress hangs on the "Your tests are loading." page: So I clicked Allow and was directed the App Management settings and I enabled Terminal:īut the result is the same. When using Terminal the os indicated that Terminal had no permissions access or modify apps. It hangs on "Opening component testing in Chrome".Ĭan you try eliminating non-default apps from the execution chain to see if there's an OS permissions issue somewhere? For example, use Terminal instead of iTerm ![]() If I run "cypress open", then using Chrome it doesn't even open the tests. What about if you step through the Cypress launch steps manually? (not provide the -component or -browser flags via CLI and instead use the UI) Using the Firefox, it hangs on "Opening component testing in Firefox". Yes, Electron hangs on the "Loading your tests" page. React App with webpack, not Create React App.ĭo you see similar behavior for other browsers (Electron, for example)? debug() function inside a test, but my tests aren't even loading.Ĭould you provide a bit of info about what sort of project you're running component tests on? Create React App? Next? Vue? Hi you run Cypress in debug mode mode and print or attach the entire set of logs here?Ĭan you be a bit more specific about what you would like me to do? I see that you can use the. I also cleared the Cypress cache and re-installed.Īny suggestions would be welcome. ![]() If I run sudo yarn cypress open -component the tests load, but when I try to run one, it just hangs here: I'm guessing that if he made similar changes he would have the same issues. I had also freshly cloned our repo and did a yarn install after the upgrade which he didn't do. But he didn't install a new node version after upgrading or make any other changes. Using node 19, yarn cypress run -component -browser chrome hangs here on the first test:Īnother member on my team only had to give App Management rights to iTerm and Webstorm and Cypress is working. I installed node 19 after upgrading to Ventura and both commands hang using version 19. But yarn cypress open -component hangs as above. ![]() With node 16, yarn cypress run -component -browser chrome still works. I had node 16 installed before upgrading to Ventura. I tried givng iTerm Full Disk Access, App Management rights, and added it to Developer Tools (all under Privacy and Security).Ĭypress hangs here ( yarn cypress open -component): After upgrading to Ventura, Cypress component testing has stopped working. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |