Docs: https://docs.cypress.io | Issues: https://github.com/cypress-io/cypress/issues
The styled problem was easy to reproduce with an existing public project of mine. I opened cypress-io/cypress#15879
i am using cy.writefile for updating an existing json file in fixtures. But am unable to see any changes made to file. However, if i print the content of file after cy.write file, i see the updated content in console but the file doesn't get updated.. Below is my code snippet:
const path = require("path");
const dir = path.join(__dirname, "../../fixtures/");
const newFilePath = path.join(dir, "hello.json")
const dirpath = path.join(dir, afixture.name);
cy.readFile(dirpath).then((obj) => {
obj.password = 'MyNewPassword123'
cy.writeFile(dirpath, JSON.stringify(obj))
}) Fixture File Before running the script is :
{
"username": "testA1213",
"password": "Admin123$"
}
It remains same after running the file.
Console output however is showing the content of the file has changed:
@jabansal2 fixtures are loaded just once, so any modifications are NOT reflected. I opened an issue cypress-io/cypress-documentation#3814 to explain it slightly better
Has anyone seen a cross origin error where the two origins noted in the error are the same?
Example:
Example:
Cypress detected a cross origin error happened on page load:
> Blocked a frame with origin "http://localhost:3000" from accessing a cross-origin frame.
Before the page load, you were bound to the origin policy:
> http://localhost:3000@jabansal2 fixtures are loaded just once, so any modifications are NOT reflected. I opened an issue cypress-io/cypress-documentation#3814 to explain it slightly better
Thanks for reverting @bahmutov . Is there a way to accomplish in cypress, what i am intending to do. So basically i am using the username and password from fixtures to login to my application. My usecase is to change the password of the account i am accessing using credentials in this fixtures file and i am trying to update the password in the fixtures file as well. So can this not be accomplished in cypress as you are mentioning that fixtures only are loaded just once? Any more inputs will be appreciated. In additions thanks for creating an issue as mentioned :).
In implementing the Cypress GitHub Action, it throws the following error after installing Cypress, but before running any of the tests: ERR! Cannot read property 'length' of undefined. Has anyone run into this issue before? I enabled the debugging logs to see if I could get any more information, but this is all it gives me around that error:
2021-04-08T20:22:55.906Z cypress:cli finished installation in /home/runner/.cache/Cypress/6.4.0
[20:22:55] Finishing Installation [completed]
25h
You can now open Cypress by running: node_modules/.bin/cypress open
https://on.cypress.io/installing-cypress
25hnpm ERR! Cannot read property 'length' of undefined
npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/_logs/2021-04-08T20_22_56_966Z-debug.log
##[debug]The process '/usr/local/bin/npm' failed with exit code 1
##[debug]Error: The process '/usr/local/bin/npm' failed with exit code 1
##[debug] at ExecState._setResult (/home/runner/work/_actions/cypress-io/github-action/v2/dist/index.js:1066:25)
##[debug] at ExecState.CheckComplete (/home/runner/work/_actions/cypress-io/github-action/v2/dist/index.js:1049:18)
##[debug] at ChildProcess.<anonymous> (/home/runner/work/_actions/cypress-io/github-action/v2/dist/index.js:943:27)
##[debug] at ChildProcess.emit (events.js:210:5)
##[debug] at maybeClose (internal/child_process.js:1021:16)
##[debug] at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
Error: The process '/usr/local/bin/npm' failed with exit code 1
##[debug]Node Action run completed with exit code 1
##[debug]CI='1'
##[debug]CYPRESS_CACHE_FOLDER='/home/runner/.cache/Cypress'
##[debug]npm_config_cache='/home/runner/.npm'
##[debug]Finishing: Cypress runFor our action, we first get the deploy preview url from Netlify before moving onto the Cypress action. Here is the full GitHub action .yml file:
name: Cypress tests
on: [push]
jobs:
cypress-tests:
runs-on: ubuntu-latest
steps:
- name: Wait for Netlify Deploy
uses: probablyup/wait-for-netlify-action@3.2.0
id: waitForDeployment
with:
site_id: ${{ secrets.NETLIFY_SITE_API_ID }}
env:
NETLIFY_TOKEN: ${{ secrets.NETLIFY_TOKEN }}
- name: Checkout
uses: actions/checkout@v2
- name: Cypress run
uses: cypress-io/github-action@v2
env:
DEBUG: 'cypress:*'
with:
browser: chrome
headless: true
record: true
config: baseUrl=${{ steps.waitForDeployment.outputs.url }}
also anyone else lol ^
@jgarrow enable the github action debug first, but also I would try the newer Cypress versions https://github.com/cypress-io/github-action#debugging
@jameseg can you create a repo with a signalr application so we can see it and what is going wrong? And open a discussion or an issue describing what is not working
@angiedaley Cypress.moment was deprecated for a while and has been removed from Cypress v7 https://on.cypress.io/changelog#7-0-0
Hi guys! I am testing an application where I need to check if a download file functionality is working properly. Is there anyway I can check through Cypress if the file is downloaded ? Currently I use cy.exec to list the directory contents and grep for the filename. Is there any other way through cypress ? Thanks
can you please any one help me on this error "cy.find() failed because this element is detached from the DOM."
6 replies
cy.find('img'). should('be.visible') seems a bit hacky, and it wouldn't work for background images
@slikts you would need to wait for the image to load, which you can check, see https://github.com/cypress-io/cypress-example-recipes/tree/master/examples/testing-dom__wait-for-resource I also suggest reading https://www.cypress.io/blog/2020/10/02/debug-a-flaky-visual-regression-test/
hello everybody. A couple questions regarding the env file - cyprss.env.json
- Do I need to store inside the cypress folder, in core project directory, or anywhere ?
- Can I access it from the command.js file. The docs says - "From test file". Does command.js considered as "test file" or not?
Pretty much my issue is I have cypress.env.json file and I try to access it from the commands .js file by Cyppres.env('key') and getting undefined
@bahmutov it was a typo in my code, sorry to bother.
after fixing, in case if anyone else have the same questions
Do I need to store inside the cypress folder, in core project directory, or anywhere ? - cypress.env.json can be stored anywhere in the project
Can I access it from the command.js file. The docs says - "From test file". Does command.js considered as "test file" or not? - the env file can be access from command.js or from test folders
after fixing, in case if anyone else have the same questions
Do I need to store inside the cypress folder, in core project directory, or anywhere ? - cypress.env.json can be stored anywhere in the project
Can I access it from the command.js file. The docs says - "From test file". Does command.js considered as "test file" or not? - the env file can be access from command.js or from test folders
@okyrylenko I would store the env file next to cypress.json I believe and commands files are considered test files as well. If an env variable is missing we would need a reproducible example and an issue to debug it. I would also read https://on.cypress.io/environment-variables
@bahmutov my issue is fixed. thank you. Also, based on this page https://auth0.com/blog/end-to-end-testing-with-cypress-and-auth0/, the suggestion is to add env file in the root directory( as you mentioned above). Maybe it would be nice to add this piece of information to https://on.cypress.io/environment-variables since that is the first page users explore when they need info on env variables
@bahmutov what I meant is that it would be nice to add information of where environmental variable can be stored in official cypress documentation. As of now, the official cypress docs says - "You can create your own cypress.env.json file that Cypress will automatically check". as you can see, there is no mentioning of where the env file could be stored(root, cypress directory, anywhere etc.) That could safe some time debugging if something goes wrong with reading data from env file and also for you answering questions like mine :)
I dont know why i started getting this error in the screenshot. Can anyone please help.
What do you all suggest for connecting to an Oracle DB from a Cypress test? My thought was: if Cypress could execute a Java .jar/class then i could just make a Java JDBC connector. I want to avoid using Oracle native type-1 driver, if possible because that requires an install outside of npm right? My tests need to run from a build machine where I cannot install stuff into.
@jabansal2 the test is running in the browser, thus there is no
process object, since this is not Node
@djangofan in general you want to connect to the database from the plugin file
Hi guys can you take a look at this thread? https://stackoverflow.com/questions/67043398/problems-with-cypress-in-a-windows-pc i'm desperate, i should be presenting cypress this week to my company
@arun86gupta this might help https://docs.cypress.io/guides/testing-strategies/google-authentication#Google-Developer-Console-Setup
@rainnxv_twitter it looks like it takes a really long time to fetch the sites assets. Are you using the same browser on each machine? Check version, etc. Does one have a different proxy setup? To me, it sounds and looks like a networking issue. Does this happen when you use the Cypress UI or only headless?
@arun86gupta this might help https://docs.cypress.io/guides/testing-strategies/google-authentication#Google-Developer-Console-Setup
@olore_twitter Thank you Brian.
@bahmutov After several tests I can confirm that it was something about Chrome not working, despite having the latest version.
Hi to all! hope you can help me with an issue. I'm on Windows 10, cypress 7.0.1, and I'm missing chrome as a browser. It doesn't show up on the right menu. Only firefox, edge and electron. I have chrome 89 on the default directory ("C:\Users\el_ra\AppData\Local\Google\Chrome\Application\chrome.exe"). I tried everything I found on the web, even a Symbolic link, but the problem persists
Hi guys! I am testing an application where I need to upload a json file. I have installed cypress-file-upload node module and I was able to upload the files when testing on some different websites. But when I use it to test my application, the application throws an error stating that the file is not in JSON format when the file actually is in JSON format. If I manually upload the same file, it works. This is the command I am using to upload the file through Cypress. cy.get('[data-id="importFile"]').attachFile(filePath); . Any suggestions? Thank you
