waitUrlEquals fails on a false-positive

[neutraali]

Problem: waitUrlEquals triggers an error even though the assertion should pass.

Code:

Scenario('navigation & routing', async function(I) {
	I.amOnPage('http://localhost:8080');
	I.click('Buttons', '.side-panel');
	I.waitUrlEquals('/buttons/single', 2); // <<< ERROR
});

Result:

-- FAILURES:
  1) Example test
	navigation & routing:
	expected url to be http://localhost:8080/ui/buttons/single, but found:
	http://localhost:8080/ui/buttons/single

Is there something I'm doing wrong or is this just a plain bug 🪲 ?

[Vorobeyko]

after click button - opens new url?

[neutraali]

after click button - opens new url?

Yeah - First the test should be at the base URL (localhost:8080). Clicking the button should trigger navigation to /buttons/single, which it does.

The weird part comes next when it tries to verify that URL is correct, which it apparently is? The test still fails though.

[Vorobeyko]

new url opens in current context? Or in new tabs?

[neutraali]

new url opens in current context? Or in new tabs?

Our application is an SPA, so the "new" URL opens in the current context / same tab.

[Vorobeyko]

Do you use Puppeteer or WDIO?

[neutraali]

Do you use Puppeteer or WDIO?

Puppeteer - Here's the config:

helpers: {
   Puppeteer: {
      url: 'http://localhost:8080' + ((config.ci === true) ? '/ui' : ''),
      windowSize: `${SCREEN_WIDTH}x${SCREEN_HEIGHT}`,
      restart: false,
      waitForNavigation: [ 'domcontentloaded' ],
      waitForAction: 1000,
      chrome: {
         executablePath: '/usr/bin/chromium-browser',
         args: ['--disable-dev-shm-usage', '--no-sandbox', '--headless', '--disable-gpu']
      }
   }
}

[Vorobeyko]

what do puppeteer version you use?

[Vorobeyko]

I can`t reproduce this defect (

[Vorobeyko]

and what do codeceptjs version you use?

[Vorobeyko]

ohhhh
i understand)))

You use waitUrlEquals - and arg must be full url path)
For wait part of url please use waitInUrl

[Vorobeyko]

although

[neutraali]

Thanks for pointing me in the right direction @Vorobeyko. I got our pipelines working using waitUrlEquals; I just had to include the absolute URL.

I guess I got things mixed up with I.amOnPage where I thought that the relative URL would resolve to the base URL defined in the config, such as localhost:8080/ui in our case.

Again, many thanks. 😸

EDIT: I mean, I guess it does resolve correctly, but the assertion for just the relative URLs is broken for waitUrlEquals. I also tried waitInUrl but that one didn't work with relative URLs either.

[neutraali]

Nah, looks like the test success was a fluke of some sort.

We're back to getting expected url to be http://localhost:8080/example/path, but found http://localhost:8080/example/path.

I.waitUrlEquals(`${BASE_URL}/example/path`)

EDIT: The confusing part here is that sometimes it works, and sometimes it doesn't. Dunno where to start debugging this one.