skills.rest
onsi
onsiCOMMUNITY
Explore all skills by this author →
GitHub

setup

Wire Biloba into a Ginkgo suite with SynchronizedBeforeSuite and Chrome lifecycle options.

25|7|Updated Mar 3, 2023
Search Tags:#automation#testing#setup#bootstrap#ginkgo#chrome-headless#biloba
One-click install
npx skills add https://github.com/onsi/biloba --skill setup-onsi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/onsi/biloba/tree/main/plugins/biloba/skills/setup
Command: npx skills add https://github.com/onsi/biloba --skill setup-onsi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wire Biloba into a project's Ginkgo test suite by providing the bootstrap wiring, Chrome lifecycle choices, and shell setup so tests can run in parallel with a stable browser.

Core Features & Use Cases

  • One-time wiring: add Biloba and bootstrap the suite with a SynchronizedBeforeSuite, Prepare, and per-process or per-spec variations.
  • Chrome lifecycle customization: choose headless-shell or full headless Chrome and set window size.
  • Easy migration: upgrade or adjust bootstrap without rewriting tests.

Quick Start

Bootstrap Biloba in your repo by running the commands in the guide and wire the suite to spin up and connect to Chrome.

Frequently Asked Questions about setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bootstrap Biloba in a Ginkgo test suite?▼

To bootstrap Biloba in a Ginkgo test suite, you add the dependency and wire SynchronizedBeforeSuite with Prepare to spin up and connect to Chrome for parallel testing.

How do I run Chrome headless in Ginkgo parallel tests?▼

Run Chrome headless in Ginkgo parallel tests by configuring the bootstrap wiring to use headless-shell or full headless Chrome, ensuring a stable browser lifecycle across test processes.

What is the difference between shared and per-process browser setup in Ginkgo?▼

Shared browser setup uses one Chrome instance across the suite, while per-process setup spins up individual browsers for parallel Ginkgo tests, configured during the SynchronizedBeforeSuite wiring.

Can I set the window size for headless Chrome in Ginkgo tests?▼

Yes, you can set the window size for headless Chrome by configuring the Chrome lifecycle options during the Biloba bootstrap setup in your Ginkgo suite.

Do I need to rewrite tests when updating my Ginkgo bootstrap setup?▼

No, you do not need to rewrite tests when updating the Ginkgo bootstrap setup, because the wiring adjustments cover bootstrap variations and Chrome lifecycle choices without touching existing tests.

What is headless-shell mode for Chrome in Ginkgo testing?▼

Headless-shell mode is a Chrome lifecycle option available during Biloba bootstrap that provides a lightweight headless browser environment for running Ginkgo tests.

Related Skills

Explore More Software Engineering Skills→
futureteafuturetea

Ginkgo Testing

Implement BDD-style Go test workflows with Ginkgo and Gomega.

Community
Advanced
ajilantonyajilantony

chrome-devtools

Automate browser interactions and inspections via the Chrome DevTools Protocol.

Community
Advanced
proffesor-for-testingproffesor-for-testing
436

compatibility-testing

Validate web application compatibility across browsers and devices with Playwright and BrowserStack.

Community
Advanced
onsionsi
25

overview

Explains Biloba's Ginkgo/Gomega-based browser testing mental model for onboarding new users.

Community
Basic