You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it("is displaying the login panel and log in is working",()=>{cy.visit("/customers/telephony",{failOnStatusCode: false}).getByText("LOGIN").click().getByTestId("phone-panel");});
What you did:
I'm trying to run Cypress from a Azure Release Pipeline. My steps:
1) Telephony
is displaying the login panel and log in is working:
TypeError: cy.visit(...).getByText is not a function
at Context.<anonymous> (https://siteurl****.z6.web.core.windows.net/__cypress/tests?p=cypress\integration\integration\customers\telephony\telephony.spec.js-039:8:8)
Problem description:
When I run my test locally (against the same baseUrl) I don't have this issue, while I use the same devDependencies and yarn to install them.
The text was updated successfully, but these errors were encountered:
I didn't create the tests, I just need to implement them on our dev-ops environment. In none of our spec files we import anything. But you made me realize that I was only using the spec files on the release pipeline. I took a look in our Cypress folder structure and found a file commands.js which has import "@testing-library/cypress/add-commands"; removing this line causes the same issues locally as on the release pipeline environment. So instead of only using the spec files, I've uploaded the entire Cypress folder and now I have the same results on the release pipeline as locally :).
dom-testing-library
version: 5.0.0react
version: 16.8node
version: v10.16.0npm
(oryarn
) version: 6.9.0Relevant code or config:
What you did:
I'm trying to run Cypress from a Azure Release Pipeline. My steps:
npm i yarn
yarn
node mochawesomereport.js
Relevant files:
cypress.json
package.json
mochawesomereport.js
What happened:
Everything is installed and Cypress runs:
Problem description:
When I run my test locally (against the same baseUrl) I don't have this issue, while I use the same devDependencies and yarn to install them.
The text was updated successfully, but these errors were encountered: