https://cypress.io logo
Join DiscordCommunities
Powered by
# general-chat
  • c
    if we use webpack for component testing then it shouldnt be an issue because the smae webpack used by react is working fine? It fails only when I try to import a file which inturn imports an image file to run e2e testing
  • b
    Why don't you use the webpack file-preprocessor?
  • b
  • b
    this way you are guaranteed to have loaders and tools that work in a modern toolchain
  • c
    wow thanks so much, why didn i bump into this earlier. i wonder if cypress/browserify is mentioned somewhere in documetns
  • c
    Using webpack preprocessor indeed did solve the issue, although the source maps are off now, although the devtools value is set in the webpack options it just doesnt seem to consider the cypress test files, I wonder if i should be specifying some entry for the webpack options
  • c
    nvm got it to work
  • u
    does anyone of Cypress know if the socketio is wss or ws? Or does it depends on the base url of the test cases?
  • w
    Hi folks, I come across from https://www.reddit.com/r/QualityAssurance/comments/o5dnup/is_there_any_http_endpoints_test_project_that/? , and tried to kick off the first endpoint case as:
  • w
    Copy code
    js
cy.request('POST', 'http://int.oa.com:8080', { bookId: '383' }).then(
  (response) => {
    // response.body is automatically serialized into JSON
    expect(response.body).to.have.property('bookId', '383') // true
  }
)
  • w
    But I got an error when tried to run it in browser as
  • g
    everything you do that calls 
    cy...
    commands should be in a test. So put your 
    cy.request
    inside an 
    it('loads', () => ....)
    test
  • w
    It works! You make my day, awesome thanks @User
  • g
    That's what I do...
  • q
    Hi, I'm Sefi, A new cypress user, my goal is to define cypress tests to run on each pull request from the development team workflow, we use Bitbucket for the application repositories & Bitbucket for the cypress automation repository as well, we're working with the cypress dashboard. the cypress repository running the tests on a cypress predefined docker image & for each bitbucket pull request from the cypress repository the image up & runs the tests, now i need to define step in the bitbucket.yml for the applications repositories, how can i define cypress run tests from the cypress automation repository to run while the application bitbucket pull request happned?
  • f
    Is there a Cypress only way to mocking 
    next/router
    like what is discussed here - https://github.com/vercel/next.js/issues/7479
  • f
    Or do I need to integrate jest to handle mocking within my component tests
  • u
    How can i acess Cloudflare DDos protected sites in Cypress
  • b
    @User this is a great question. If you are using e2e testing, you should mock the routes directly using 
    cy.intercept()
    . If you are using CT, then one can stub or spy on any module in mocha. Check out this example. https://github.com/elevatebart/cy-nextjs/blob/main/components/DisplayRoute/DisplayRoute.spec.jsx
  • b
    The only issue you will face here is that one can only mock a es5 module, not a es6 version. To fix this, you will have to babelify your code in testing.
  • f
    Applying this to my test was able to get it to render for a split second, then gives me the error
    Copy code
    Error: TypeError: router.prefetch is not a function
    . This is how I organized my test:
    Copy code
    js
import { mount } from '@cypress/react'
import * as nextRouter from 'next/router'
import Navbar from '../../component/Navbar'

const LINKS = [
  { text: 'Home', to: '/' },
  { text: 'About', to: '/about' },
  { text: 'Ninja Listing', to: '/ninjas' },
]

describe('<Navbar />', () => {
  it.only('displays links', () => {
    cy.stub(nextRouter, 'useRouter').callsFake(() => ({ pathname: '/' }))
    mount(<Navbar links={LINKS} />)
  })
})
  • b
    can you add 
    prefetch()
    to the pathname ?
  • b
    cy.stub(nextRouter, 'useRouter').callsFake(() => ({ pathname: '/', prefetch: sinon.stub() }))
  • b
    the principle you want to follow is to fake all functions that will be using to have them be predictable
  • f
    Hey guys, question about cypress. I'm testing a game I made and this line of code it doesn't work as I expected: arrMatchingCards = Object.values(cardsMap)
  • w
    What I think is happening here is not cypress specific ... 
    getMatchingCards
    returns an empty object right away, because 
    matchingCards
    is initialized as empty and the work to populate it all happening asynchronously. So the 
    Object.values(arrMatchingCards)
    is called when 
    arrMatchingCards
    is still just 
    {}
    - which would explain the empty array at that point. Meanwhile everything in the 
    .then
    of your 
    cards.each
    is happening asynchronously, and since the JS console is showing a live representation of the object, those property assignments appear in the console even though they actually happened to the object after line 41 ran. If this is right, something like 
    console.log(JSON.stringify(cardsMap))
    instead of logging the raw object would verify, as it would log an empty object. Same issue would apply where you console log 
    matchingCards
    inside your function - it's logging a reference to the live object.
  • f
    Thank u @User . This's what i did
  • f
    Does anyone know why this happens?
  • f
    I've run into this error and a couple just like this. I found this article to be helpful in understanding what's happening: https://www.cypress.io/blog/2021/01/26/when-can-the-test-blink/
  • u
    how do you assert without/skipping cy.get?
1...101112...127Latest