cy.url not returning a string as expected
Asked Answered
T

2

5

Prior to switching to using a hash router, I had been implementing the cy.url command frequently to assure that links were navigating to the right URL addresses throughout the application. Now that we are using hash routing cy.url no longer yields a string, instead it is yielding a function. Any ideas how to work around this or reasons this is happening?

I was getting errors through out the cypress test runner like:

AssertionError: object tested must be an array, an object, or a string, but undefined given

so I logged the typeof result console.log(typeof(cy.url)) and got function printed to the console.

cy.get(dataCyButtonAttribute)
    .should('be.visible')
    .click()
  console.log(typeof(cy.url))
  cy.url().then(url => {
    const categoryId = url.split(`${linkType}/`)[1]
    const category = url.split('admin/')[1]
    expect(category).to.contain(linkType)
    expect(categoryId).to.equal('new')
  })
}
Turtle answered 21/6, 2019 at 20:44 Comment(1)
Can you share an example GitHub repository that shows this behavior? I tried to reproduce this using your example, but cy.url always yields a string for me.Phenomenon
K
7

This should yield a string:

const returnedUrl = null
cy.url().then(url => {
  returnedUrl = url;
});

Cypress commands are asynchronous and must be followed by .then() in order to yield useful return values.

You can refer to this Github issue for more info: https://github.com/cypress-io/cypress/issues/2150

Kellene answered 15/7, 2019 at 19:24 Comment(0)
F
0

I have encountered the same issue. And my solution as below.

      cy.url().then(($base_url) => {   
        let id =  $base_url.substr($base_url.lastIndexOf('/'),$base_url.length) 
        cy.log("The id is " + id);
       })

It works for me.

Faroff answered 12/3, 2020 at 9:32 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.