# Headless Browser

A browser operating mode that runs a browser in an unattended environment without a visible user interface. It is used with browser-automation tools and automated tests.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Vercel Functions can now run up to 30 minutes

DevFeed: [Vercel Functions can now run up to 30 minutes](<https://devfeed.tech/articles/vercel-functions-can-now-run-up-to-30-minutes-1151.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-functions-can-now-run-up-to-30-minutes>)

Author: Tiago Ventura Loureiro

Published: 2026-06-15T14:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [Python](<https://devfeed.tech/topics/python.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Next.js](<https://devfeed.tech/topics/next-js.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [Headless Browser](<https://devfeed.tech/topics/headless-browser.md>), [Web Scraping](<https://devfeed.tech/topics/web-scraping.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [apis](<https://devfeed.tech/tags/apis.md>), [automation](<https://devfeed.tech/tags/automation.md>), [browser](<https://devfeed.tech/tags/browser.md>), [cost](<https://devfeed.tech/tags/cost.md>), [llm](<https://devfeed.tech/tags/llm.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [python](<https://devfeed.tech/tags/python.md>), [vercel](<https://devfeed.tech/tags/vercel.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

Vercel Functions running on Node.js and Python can now execute for up to 30 minutes for Pro and Enterprise teams. The update supports longer-running workloads such as LLM reasoning, streamed AI responses, document and media processing, OCR, web scraping, browser automation, workflow steps, and queue handlers.

### Source excerpt

Vercel Functions using the Node.js and Python runtimes now support execution durations up to 30 minutes for Pro and Enterprise teams, more than 2x the previous 800 second limit. Support for additional runtimes is coming soon. Use longer-running Functions for work that needs more time to finish, including: Long LLM reasoning and tool calls AI responses that stream for several minutes Document and media processing OCR and extraction Web scraping and browser automation Complex Workflow steps or Queue handlers Fluid compute keeps long-running work cost-efficient. Active CPU billing only applies while your code is executing, and pauses while your Function is waiting on I/O such as AI model calls, database queries, and third-party APIs. Set maxDuration to opt in. For Next.js App Router, configure it in the route file: For other runtimes and frameworks, configure maxDuration for a specific function path in vercel.json: Durations above 800 seconds are in beta and require Fluid compute. Learn more about configuring max duration for Vercel Functions in the documentation. Read more

## Testing a React App in Chrome with Heroku CI

DevFeed: [Testing a React App in Chrome with Heroku CI](<https://devfeed.tech/articles/testing-a-react-app-in-chrome-with-heroku-ci-26500.md>)

Original publisher: [Read original article](<https://www.heroku.com/blog/testing-react-app-chrome-heroku-ci/>)

Author: Julián Duque

Published: 2024-09-24T20:11:00Z

Content type: tutorial

Language: en

Sources: [Heroku](<https://devfeed.tech/sources/heroku.md>)

Topics: [React](<https://devfeed.tech/topics/react.md>), [Heroku](<https://devfeed.tech/topics/heroku.md>), [ci](<https://devfeed.tech/topics/ci.md>), [Playwright](<https://devfeed.tech/topics/playwright.md>), [Puppeteer](<https://devfeed.tech/topics/puppeteer.md>), [Headless Browser](<https://devfeed.tech/topics/headless-browser.md>), [Testing](<https://devfeed.tech/topics/testing.md>), [Jest](<https://devfeed.tech/topics/jest.md>), [web applications](<https://devfeed.tech/topics/web-applications.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [ci](<https://devfeed.tech/tags/ci.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [download](<https://devfeed.tech/tags/download.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [github](<https://devfeed.tech/tags/github.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [guide](<https://devfeed.tech/tags/guide.md>), [heroku](<https://devfeed.tech/tags/heroku.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [jest](<https://devfeed.tech/tags/jest.md>), [react](<https://devfeed.tech/tags/react.md>), [testing](<https://devfeed.tech/tags/testing.md>), [unit-testing](<https://devfeed.tech/tags/unit-testing.md>), [web-applications](<https://devfeed.tech/tags/web-applications.md>)

### AI overview

This tutorial explains how to run end-to-end tests for a React application in Heroku CI using headless Chrome, Jest, and Puppeteer. It covers automating tests for a simple form-based application and configuring the application and test scripts for CI execution.

### Source excerpt

When building web applications, unit testing your individual components is certainly important. However, end-to-end testing provides assurance that the final user experience of your components chained together matches the expected behavior. Testing web application behavior locally in your browser can be helpful, but this approach isn't efficient or reliable, especially as your application grows more [...] The post Testing a React App in Chrome with Heroku CI appeared first on Heroku.

## Interop 2023: MDN updates

DevFeed: [Interop 2023: MDN updates](<https://devfeed.tech/articles/interop-2023-mdn-updates-4069.md>)

Original publisher: [Read original article](<https://developer.mozilla.org/en-US/blog/interop2023-mdn-doc-updates/>)

Author: brian-smith

Published: 2024-03-27T00:00:00Z

Content type: article

Language: en

Sources: [MDN Blog](<https://devfeed.tech/sources/mdn-blog.md>)

Topics: [Web platform](<https://devfeed.tech/topics/web-platform.md>), [interoperability](<https://devfeed.tech/topics/interoperability.md>), [Interop2027](<https://devfeed.tech/topics/interop2027.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [browsers](<https://devfeed.tech/topics/browsers.md>), [Headless Browser](<https://devfeed.tech/topics/headless-browser.md>), [Mozilla](<https://devfeed.tech/topics/mozilla.md>)

Tags: [automated](<https://devfeed.tech/tags/automated.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [interop](<https://devfeed.tech/tags/interop.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [mozilla](<https://devfeed.tech/tags/mozilla.md>), [tests](<https://devfeed.tech/tags/tests.md>), [web-platform](<https://devfeed.tech/tags/web-platform.md>)

### AI overview

This article explains the Interop project, a joint browser-vendor initiative that uses benchmarks and tests to improve consistent, standards-compliant web platform behavior across browsers. It reviews Interop 2023 updates on MDN and describes the Interop 2024 effort, including focus areas, dashboards, headless browser tests, Web Platform Tests, and browser fixes.

### Source excerpt

Interop 2023 has successfully concluded, and the Interop 2024 project is now officially underway. Learn what Interop is, discover the updates from Interop 2023 now on MDN, and find out what's coming to the web next.

## Create a CD pipeline with Angular, GitLab and Firebase

DevFeed: [Create a CD pipeline with Angular, GitLab and Firebase](<https://devfeed.tech/articles/create-a-cd-pipeline-with-angular-gitlab-and-firebase-21327.md>)

Original publisher: [Read original article](<https://juri.dev/blog/2018/02/cd-gitlab-angular-firebase/>)

Published: 2018-02-07T00:00:00Z

Content type: tutorial

Language: en

Sources: [Juri Strumpflohner](<https://devfeed.tech/sources/juri-strumpflohner.md>)

Topics: [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Angular](<https://devfeed.tech/topics/angular.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Firebase](<https://devfeed.tech/topics/firebase.md>), [Headless Browser](<https://devfeed.tech/topics/headless-browser.md>), [Angular CLI](<https://devfeed.tech/topics/angular-cli.md>), [Chrome](<https://devfeed.tech/topics/chrome.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [angular](<https://devfeed.tech/tags/angular.md>), [browser](<https://devfeed.tech/tags/browser.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [continuous-delivery](<https://devfeed.tech/tags/continuous-delivery.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [script](<https://devfeed.tech/tags/script.md>), [test](<https://devfeed.tech/tags/test.md>), [tests](<https://devfeed.tech/tags/tests.md>), [unit-tests](<https://devfeed.tech/tags/unit-tests.md>)

### AI overview

A tutorial on creating a continuous delivery pipeline for an Angular project using GitLab CI/CD and Firebase. It covers package.json build scripts, Angular CLI app-specific builds, automated tests, and running Karma tests with headless Chrome on a CI server.

### Source excerpt

Lorem ipsum dolor sit amet

## Code Coverage with QUnit in JavaScriptMVC

DevFeed: [Code Coverage with QUnit in JavaScriptMVC](<https://devfeed.tech/articles/code-coverage-with-qunit-in-javascriptmvc-21196.md>)

Original publisher: [Read original article](<https://juri.dev/blog/2013/06/code-coverage-with-qunit-in-javascriptmvc/>)

Published: 2013-06-24T00:00:00Z

Content type: tutorial

Language: en

Sources: [Juri Strumpflohner](<https://devfeed.tech/sources/juri-strumpflohner.md>)

Topics: [test-coverage](<https://devfeed.tech/topics/test-coverage.md>), [Testing](<https://devfeed.tech/topics/testing.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Mocking](<https://devfeed.tech/topics/mocking.md>), [Selenium](<https://devfeed.tech/topics/selenium.md>), [Headless Browser](<https://devfeed.tech/topics/headless-browser.md>)

Tags: [code-coverage](<https://devfeed.tech/tags/code-coverage.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [mocking](<https://devfeed.tech/tags/mocking.md>), [selenium](<https://devfeed.tech/tags/selenium.md>), [testing](<https://devfeed.tech/tags/testing.md>), [ui-testing](<https://devfeed.tech/tags/ui-testing.md>), [unit-test](<https://devfeed.tech/tags/unit-test.md>)

### AI overview

This tutorial explains how to use QUnit and FuncUnit in JavaScriptMVC to measure code coverage for JavaScript tests. It describes FuncUnit's Selenium-based web application testing capabilities, Cobertura-based coverage analysis, and a test folder structure containing QUnit files.

### Source excerpt

Lorem ipsum dolor sit amet