dc7593f978
Follow-up to the edit-mode component migration, applying a review of the new spec, page object and drag-and-drop helper. Correctness: - Resolve the dataset through getDatasetByName and create the chart through apiPostChart instead of calling page.request directly. Both wrap the request in the shared transient-retry helper, which exists because the dev server drops connections under concurrent load; the direct call had no such cover. - The resize assertion was guarded by `if (handleBox && boxBefore)` while only handleBox was asserted non-null, so a null bounding box silently skipped the assertion and the test still passed. DashboardPage.resizeComponent now throws on a missing box and returns the before/after heights for the spec to assert. - Replace the deprecated Locator.type() with pressSequentially(). Reuse over duplication: - Drop the local dashboard-creation helper in favour of createTestDashboard, which already handles both response shapes and cleanup registration; it gains an optional `published` flag. Chart ids come from extractIdFromResponse. - Generated names use the worker's parallel index, matching the convention in the sibling helpers, rather than a performance.now() suffix. Page object and readability: - Move the ace, resize-handle and title selectors out of the spec behind DashboardPage accessors. These stay locators rather than routing through the AceEditor component, whose setText/getText work through the ace API and so would bypass the keystroke path under test and lose web-first retries. - Name the react-dnd settle delay and the markdown retry budgets. - Make openBuilderTab private, drop the unused deleteChartHolder index, remove the unused GRID_CONTENT selector, correct the dropTarget docstring, type layout-element labels as a union, and prefix the locator getters with `get` to match the rest of the class. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Superset
A modern, enterprise-ready business intelligence web application.
Documentation
- User Guide — For analysts and business users. Explore data, build charts, create dashboards, and connect databases.
- Administrator Guide — Install, configure, and operate Superset. Covers security, scaling, and database drivers.
- Developer Guide — Contribute to Superset or build on its REST API and extension framework.
Why Superset? | Supported Databases | Release Notes | Get Involved | Resources | Organizations Using Superset
Why Superset?
Superset is a modern data exploration and data visualization platform. Superset can replace or augment proprietary business intelligence tools for many teams. Superset integrates well with a variety of data sources.
Superset provides:
- A no-code interface for building charts quickly
- A powerful, web-based SQL Editor for advanced querying
- A lightweight semantic layer for quickly defining custom dimensions and metrics
- Out of the box support for nearly any SQL database or data engine
- A wide array of beautiful visualizations to showcase your data, ranging from simple bar charts to geospatial visualizations
- Lightweight, configurable caching layer to help ease database load
- Highly extensible security roles and authentication options
- An API for programmatic customization
- A cloud-native architecture designed from the ground up for scale
Screenshots & Gifs
Video Overview
Large Gallery of Visualizations
Craft Beautiful, Dynamic Dashboards
No-Code Chart Builder
Powerful SQL Editor
Supported Databases
Superset can query data from any SQL-speaking datastore or data engine (Presto, Trino, Athena, and more) that has a Python DB-API driver and a SQLAlchemy dialect.
Here are some of the major database solutions that are supported:
A more comprehensive list of supported databases along with the configuration instructions can be found here.
Want to add support for your datastore or data engine? Read more here about the technical requirements.
Installation and Configuration
Try out Superset's quickstart guide or learn about the options for production deployments.
Get Involved
- Ask and answer questions on StackOverflow using the apache-superset tag
- Join our community's Slack and please read our Slack Community Guidelines
- Join our dev@superset.apache.org Mailing list. To join, simply send an email to dev-subscribe@superset.apache.org
- Follow us on social media: X | LinkedIn | Bluesky | Reddit
- If you want to help troubleshoot GitHub Issues involving the numerous database drivers that Superset supports, please consider adding your name and the databases you have access to on the Superset Database Familiarity Rolodex
- Join Superset's Town Hall and Operational Model recurring meetings. Meeting info is available on the Superset Community Calendar
Contributor Guide
Interested in contributing? Check out our Developer Guide to find resources around contributing along with a detailed guide on how to set up a development environment.
Resources
- Superset "In the Wild" - see who's using Superset, and add your organization to the list!
- Feature Flags - the status of Superset's Feature Flags.
- Standard Roles - How RBAC permissions map to roles.
- Superset Wiki - Tons of additional community resources: best practices, community content and other information.
- Superset SIPs - The status of Superset's SIPs (Superset Improvement Proposals) for both consensus and implementation status.
Understanding the Superset Points of View
-
Getting Started with Superset
-
Deploying Superset
-
Recordings of Past Superset Community Events
-
Visualizations
