Files
superset2/docs/developer_docs/testing/frontend-testing.md
Evan Rusackas 0fb7fc2721 docs: bifurcate documentation into user, admin, and developer sections
Major restructuring of documentation to separate concerns:

**New Structure:**
- `/docs/` - User-facing docs (intro, quickstart, databases, using-superset, faq)
- `/admin-docs/` - Administrator docs (installation, configuration, security)
- `/developer-docs/` - Developer docs (contributing, extensions, guidelines, testing)

**Changes:**
- Move installation, configuration, and security docs to admin_docs/
- Move contributing, extensions, guidelines, and testing to developer_docs/
- Rename developer_portal to developer_docs (with underscore to hyphen in URL)
- Add sidebarAdminDocs.js for admin documentation navigation
- Update versions-config.json with new doc sections
- Update docusaurus.config.ts with new plugins and redirects
- Update internal links in versioned docs (6.0.0) to use new paths
- Keep user-facing content (databases, using-superset, faq) in main docs

This separation makes it clearer which documentation is relevant for:
- End users exploring and visualizing data
- Administrators deploying and configuring Superset
- Developers contributing to or extending Superset

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-02-24 11:41:27 -08:00

1.5 KiB

title, sidebar_position
title sidebar_position
Frontend Testing 2

Frontend Testing

🚧 Coming Soon 🚧

Comprehensive guide for testing Superset's frontend components and features.

Topics to be covered:

  • Jest configuration and setup
  • React Testing Library best practices
  • Component testing strategies
  • Redux store testing
  • Async operations and API mocking
  • Snapshot testing guidelines
  • Coverage requirements and reporting
  • Debugging test failures
  • Performance testing for UI components

Quick Commands

# Run all frontend tests
npm run test

# Run tests in watch mode
npm run test -- --watch

# Run tests with coverage
npm run test -- --coverage

# Run specific test file
npm run test -- MyComponent.test.tsx

This documentation is under active development. Check back soon for updates!