is it possible to install Cypress in Windows 10 for all users? I want to install Cypress once as Admin and every other user can use it. Any hints?
Thanks
Related
So i'm making a bash script to setup my Ubuntu distro in wsl2. I'm trying to install npm so i follow the Microsoft tutorial installing nvm -> then npm with nvm install --lts.
The thing is i can't find a way to install through nvm because nvm installs but then when i run nvm install --lts it doesn't work. Now microsoft says i have to reboot the terminal and it does work that way but i wonder if i can do it via the bash script, basically reloding the shell or opening a new one to install npm?
Thanks in advance
I would actually go ahead and look for an NPM that suites your needs with SSH. I then would automate the process with both an initial setup>wait with setTimeouts/intervals till server is back online and continue setup and when server is fully ready it will then begin to respond the way you need it to. No examples unfortunately but hope this helps. :)
My setup:
OS: Ubuntu 18
Testcafe Version: 1.8.8
Browser: Firefox
I have several Ubuntu servers where Testcafe was working. Due to a security issue, I had to reinstall the servers entirely. Unfortunately in the fresh reinstall, Testcafe is saying it is unable to establish one or more of the specified browser connections. I have firefox installed and reconfirmed it was installed.
Previously I did this:
Issue command: sudo testcafe test.js
Expected behavior: After a moment, I could visibly see in the logs that the test was running using Firefox headless. Life was fine.
Now when I do the exact same thing in the fresh reinstall:
Issue command: sudo testcafe test.js
Unexpected behavior: After a moment, I get this in console:
Using locally installed version of TestCafe. ERROR Unable to establish one or more of the specified browser connections. This can be caused by network issues or remote device failure.
Bummer!
Here is the .testcaferc.json I am using:
{
"browsers": ["firefox:headless"],
"speed": 0.1,
"skipJsErrors" : true,
"pageLoadTimeout": 5000
}
When I run testcafe --list-browsers, I get:
firefox
My test file:
import { ClientFunction, Selector } from 'testcafe';
fixture `triage`
.page('https://www.google.com/');
test(`test debugging`, async t => {
await t
.wait(5000)
console.log(`I did it!`)
})
Previously there was no issue! Had I not had to reinstall Ubuntu, there would be no fail. I have actually 5 servers like this and really need a fix. Any ideas why this is happening?
I even installed chrome. Same issue! Failure to establish a connection to chrome too.
Finally this was solved for me. My solution, and what I did differently.
Previous install steps:
Install Ubuntu
Login as root
Create new user
Login to new user account
Install Node.js as sudo in new user account
Install Firefox as sudo in new user account
Install Testcafe as sudo in new user account
Setup git clone of express...
After days of looking at this I thought wait Unable to establish one or more of the specified browser connections may just mean Can't see the browser due to being installed as sudo in a user account thus unable to establish that browser connection... (like it can't see it for some reason).
To test this theory, I rearranged the install steps and suddenly everything worked!
Here are the steps that solved this issue for me:
Install Ubuntu
Login as root
Install Node.js AS ROOT
Install Firefox AS ROOT
Install Testcafe AS ROOT (this allows you to do npm i -g testcafe as well as being able to issue the command testcafe "firefox:headless" mytest.js -e instead of sudo testcafe "firefox:headless" mytest.js -e, which doesn't work with sudo well)
Create new user
Login to new user account
Setup git clone of express...
Now all my requests are triggering the tests as before.
I've written a testcase with cypress.io which is working fine.
I want that a couple of non-technical people can run this test from their local machines.
My assume was:
Install node-js on the local machines
unzip my project and change to this directory
run ./node_modules/.bin/cypress open
Problem is that the users get the error that cypress is not installed. is there any solution that the users don't have to run npm install cypress --save-dev first? in my understanding i deliver the cypress installation right within my project?
Pls see my project structure here:
on your project you should have a package.json file with cypress in it
"devDependencies": {"cypress": "^4.0.0"}
after they install nodejs, they just need to go into the folder and run npm install or npm i for short.
if you ever encounter an issue with the npm command, use npx instead
I work in a big organisation as UX designer. I have basic programming knowledge. I've been trying for ways to install node / npm on macOS without admin rights with no luck.
I've tried all the methods described here
https://gist.github.com/isaacs/579814
but all of them require using sudo or make which I cannot use
I've also downloaded the installer from nodejs.org and, unpack the file with pkgutil but when I run tar on the payloads they are copied to usr/local/bin/includes/node then I try to change the path in the host file but I need admin password to save.
I thought that this would be as easy as doing it on a Windows machine but it's not.
I installed node on my windows 8 machine with no problems and then went to install the socket.io package to use for an assignment. After typing
npm install socket.io
I got a huge amount of errors.
What I've tried so far:
this - nodejs npm install socket.io error
and this - NPM - Can't install socket.IO
The first answer in both.
A lot of the other stuff I'm finding is for either windows 7 or Mac so I'm not sure if this is just a windows 8 thing.
As you can see in logs you have a permission error. Script doesn't have enough permissions to create directory in C:\\Program_Files\.... Use other directory instead or run command with Admin permissions.
Try running
npm install socket.io
except this time run the command line as an administrator. You can do this in Windows 8 by going to your app search, typing cmd, right-clicking then click 'Run as administrator'.
I feel this is the issue because your error message says 'Please try running this command again as root/Administrator'.