mirror of
https://github.com/lobehub/lobehub.git
synced 2026-09-20 04:56:13 +08:00
Arvin Xu
ab5ec4c81d
* ♻️ refactor(agent-share): move the share surface out of the open-source tree Agent sharing runs a visitor's conversation on the creator's account and bills it to them. `ENABLE_BUSINESS_FEATURES` is `false` here, so every entry point already failed closed and the ~6k lines of surface were unreachable — while the spend cap that makes sharing safe is enforced only where that accounting lives. Its siblings `pageShare` and `artifactShare` already ship that way. Removed: the visitor and creator-settings features, their skeletons, and the `/a/*` route registrations on desktop and mobile. Kept: the table, models, tRPC procedures, runtime authorization, and the locale keys. Only the UI layer moves. Added two slots so the remaining open-source surfaces keep compiling and stay honest about the capability: - `useAgentShareSupported` reports "not supported", which hides the profile tab, the header action, and the settings page. - `AgentShareSettingsPage` renders nothing for the route those entries reach. `SharedAgentData` also gains the fields the moved profile reads — creator, tags, opening questions, reach counts, terms and granted tool identifiers — since the procedure serving them stays here. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * ✅ test(spa): stop asserting the share path as a standalone route `/a/*` is no longer defined here, so it resolves through the main layout's catch-all instead of as a standalone route. The deployment that registers the share surface asserts its own scope. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * 🔥 test(e2e): drop the agent-share keyboard scenario with its surface The `@ROUTES-003` scenario tabs to the share visitor top bar's "Go to my LobeHub" link, which left this tree along with the rest of the visitor UI. Its intent — a share link never dead-ends a visitor — is covered in the cloud repo, where the bar now lives. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
E2E Tests for LobeHub
This directory contains end-to-end (E2E) tests for LobeHub using Cucumber (BDD) and Playwright.
Directory Structure
e2e/
├── src/ # Source files
│ ├── features/ # Gherkin feature files
│ │ └── discover/ # Discover page tests
│ ├── steps/ # Step definitions
│ │ ├── common/ # Reusable step definitions
│ │ └── discover/ # Discover-specific steps
│ └── support/ # Test support files
│ └── world.ts # Custom World context
├── reports/ # Test reports (generated)
├── cucumber.config.js # Cucumber configuration
├── tsconfig.json # TypeScript configuration
└── package.json # Dependencies and scripts
## Prerequisites
- Node.js 20, 22, or >=24
- Dev server running on `http://localhost:3010` (or set `BASE_URL` env var)
## Installation
Install dependencies:
```bash
cd e2e
pnpm install
Install Playwright browsers:
npx playwright install chromium
Running Tests
Run all tests:
npm test
Run tests in headed mode (see browser):
npm run test:headed
Run only smoke tests:
npm run test:smoke
Run discover tests:
npm run test:discover
Environment Variables
BASE_URL: Base URL for the application (default:http://localhost:3010)PORT: Port number (default:3010)HEADLESS: Run browser in headless mode (default:true, set tofalseto see browser)
Example:
HEADLESS=false BASE_URL=http://localhost:3000 npm run test:smoke
Writing Tests
Feature Files
Feature files are written in Gherkin syntax and placed in the src/features/ directory:
@community @smoke
Feature: Community Smoke Tests
Critical path tests to ensure the community module is functional
@COMMUNITY-SMOKE-001 @P0
Scenario: Load community assistant list page
Given I navigate to "/community/agent"
Then the page should load without errors
And I should see the page body
And I should see the search bar
And I should see assistant cards
Step Definitions
Step definitions are TypeScript files in the src/steps/ directory that implement the steps from feature files:
import { Given, Then } from '@cucumber/cucumber';
import { expect } from '@playwright/test';
import { CustomWorld } from '../../support/world';
Given('I navigate to {string}', async function (this: CustomWorld, path: string) {
await this.page.goto(path);
await this.page.waitForLoadState('domcontentloaded');
});
Test Reports
After running tests, HTML and JSON reports are generated in the reports/ directory:
reports/cucumber-report.html- Human-readable HTML reportreports/cucumber-report.json- Machine-readable JSON report
Troubleshooting
Browser not found
If you see errors about missing browser executables:
npx playwright install chromium
Port already in use
Make sure the dev server is running on the expected port (3010 by default), or set PORT or BASE_URL environment variable.
Test timeout
Increase timeout in cucumber.config.js or src/steps/hooks.ts:
setDefaultTimeout(120000); // 2 minutes