The dependency puppeteer was updated from 2.0.0 to 2.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

puppeteer is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Allow headless/headful behaviour of Puppeteer to be controlled by a launch option.

Action that allows user to pass a comma separated list of CSS selectors which can be hidden/unhidden using visibility style. Useful for screen comparing pages with variable metadata.

The devDependency codecov was updated from 3.6.3 to 3.6.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

codecov is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

in here

i write my feature test like that:

And I click the button "[type='submit']" and wait for the element "#vue-app"

and the test will block, finally down by timeout,
but when i change the promise order, everything is good.

could you tell me why?

I have recently started working with cucumber and puppeteer. Came across the library. I just wanted to give it a try.

First I tried the example project at https://github.com/patheard/test-cuke. It works as-is out of the box.

I then tried to create my own individual project. I tried installing cucumber-puppeteer with npm install cucumber-puppeteer and in package.json it installed ^1.0.16 which is the latest release. However npm test fails with an error.

The example project https://github.com/patheard/test-cuke will not work as well with 'v1.0.16'.

I tried to check more details for the same and I found out that the https://github.com/patheard/test-cuke is still using v1.0.15 (package.lock file has it) which happens to work properly. When a version is switched to v1.0.16 there seem to be some issues with the test, which I thought was weird.

Following is the print screen when I tried to run npm test :

I could not exactly locate the issue with this. If the example project https://github.com/patheard/test-cuke itself could be updated to use with the latest release of cucumber-puppeteer that would also help.

Any help on this is appreciated. I would also like to take a moment here to thank the contributors for the development efforts on this library. Cheers.

Similar to check element visible, but a simple timeout for existence.

Allow tests to wait until the window load event has fired from the page.

In my testing setup I like to output detailed results in the command line. For that I normally use attachments to make sure the results appear on the right spot in the command line.

With your setup I can't use this.attach anymore because you don't expose that in your world constructor. Is it an idea to expose this.attach as well.

Something like:

constructor(args){
    this.browser = null;
    this.config = null;
    this.page = null;
    this.worldParameters = args && args.parameters ? args.parameters : {};
    this.attach = args && args.attach ? args.attach : null;
}

It seems that clickElement does not work on all cases. I have a regular Ext.js app and I tried on other simple ones,

let selector = 'input[name="username"]';

// does NOT work
await page.click(selector); 

// does work
await page.evaluate((selector) => document.querySelector(selector).click(), selector); 

Googling around, I am not the first person to solve it using the does work method but should the library here adhere to more verbose standards?

Allow for hardcoded values with environment variables:

When I open the url "/llisapi.dll?func=ll&objId=${FOLDER_OBJECT_ID}"

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The dependency axe-puppeteer was updated from 1.0.0 to 1.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

axe-puppeteer is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Create code and tests to determine if a DOM element has focus. The API docs for Puppeteer will help show what's possible.

1. Look for examples in the code the use page.$eval to interact with the page's DOM.
2. Try writing the unit tests first, before adding the check logic.
3. The webdriverio/cucumber-boilerplate has good examples for the given and then step definition regular expressions.

The dependency snyk was updated from 1.246.0 to 1.247.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

snyk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Is that something that will be going in or can I send in a PR for this?

Hi,
How to implement parallel execution like executing cucumber scenarios with puppeteer in many chrome instance.

Currently puppeteer.launch is used to start the browser, however, to connect to a remote instance, you need to use puppeteer.connect.

Perhaps the existence of browserWSEndpoint in the config options can be checked, and if present, use .connect over .launch?

I was curious, is there a way to have a custom variable injected. In the example/read-me, you set the url however, what if I wanted to pass an variable which changes its url depending on the environment?

• If reference screenshot, expect matches
• If no reference, take ref and fail test with warning
• Ability to resize browser during screenshot test

hi @patheard

first you set BrowserScope in here, everything good.

but when goto this line

and the first feature in, the featureScope's params are null,

in init method,

see the this.browserScope it is null,
and the worldParameters also empty,
but you use it in new BrowserScope({ parameters: worldParameters }),

so i think that is a bug.

hi all, i want to use

npm run test for headless puppeteer
npm run test:dev for head puppeteer

could you tell me how to ?

Use as a way to do partial matching on an element's attribute value.

The dependency snyk was updated from 1.252.0 to 1.253.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

snyk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

hi @patheard , could you tell me how to active the coverage ?

from this: https://pptr.dev/#?product=Puppeteer&version=v1.18.1&show=api-class-coverage

we should enable it in hook Before and after here:

right?

The devDependency snyk was updated from 1.230.5 to 1.230.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

snyk is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The dependency snyk was updated from 1.192.2 to 1.192.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

snyk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Let a downstream consumer of the lib set things like headless and sloMo.