Great post!

Since extensions must be tested in head-full mode and as far as I know in circleci only allows headless. Since it's just a linux container and doesn't have windows or any fx display.

Did you solve that issue?

I'm working on a suit test for an extension that I made and I'm running into some problems! (Happy to chat about those tho, it's definitively fun to work with chrome ext)

Cheers!

Thanks, David. I would love to chat about extensions in general. Also, I'm thinking of creating a series on the same and maybe we can do it together ;)

And with respect to the CircleCI case, I think CircleCI supports headful mode as I vaguely remember that I test this whole blog post code in CircleCI environment. However, I can check again and get back.

Great article! Small observation in "Joining all the pieces" script. `this.timeout(20000)` that's 20 seconds there, typo?

Thanks, Daniel Caldas . I guess it's not a typo. Mocha's default timeout is to be 2 seconds. But it's nearly impossible to boot up a browser and run our test. Hence I added 20 seconds as an arbitrary time. We can customize that based on the project's nature.

Oh that's true, I get now the `this.timeout` it's actually a primitive from mocha itself, makes total sense now. Thanks for the explanation gokul

a great idea to user Puppeteer for extension testing. Maybe the only topic that isn't covered in this article is the testing of extension that contains a content script. So you want to load some HTML page with sample markup into the browser and then turn on the extension for that page and run your tests.

Thanks webdevbyjoss2. Exactly as you said. May be for an another separate blog ;)

excellent post and UI, very easy to follow.

Thank you so much Guido Tarsia Glad you liked it.

I used to have problem for CI/CD of headful chrome extension testing and finally resolved with this package
https://github.com/mujo-cod...
It also has docker file of headful setup process and this link would be helpful.