web-platform-tests/wpt

Features

• Cross-Browser Testing Tools - An execution framework that runs web-platform tests across multiple browsers to verify conformance with web standards.
• Automated Pull Request Reviewers - Automatically labels pull requests by changed directory and notifies maintainers listed in META.yml files for review.
• Test Submission Reviews - Provides a process for reviewing test submissions to ensure they meet quality and specification requirements.
• Rendering Comparison Frameworks - Verifies visual output by comparing test pages against reference pages using pixel-level or structural matching.
• Test Harnesses - Provides a JavaScript-based test harness for executing browser API tests across any browser.
• Pull Request Submissions - Accepts test contributions through GitHub pull requests with automatic labeling and reviewer notification.
• Expected Outcome Registries - Ships an expectation-driven regression detection system that compares actual test outcomes against stored baselines.
• Hosted Test Interfaces - Runs the full test suite through a hosted web interface without any local setup or installation.
• Local Test Servers - Starts a local HTTP server that hosts the test suite for manual or automated browser testing.
• CI Integration Testing - Triggers full test runs in continuous integration pipelines directly from the repository.
• JavaScript Testing Frameworks - Creates tests using the testharness.js framework to verify API behavior through JavaScript assertions.
• Parallel Test Execution - Spawns multiple browser instances simultaneously to reduce total test execution time.
• Reftests - Compares two or more pages to assert they render identically or differently for layout verification.
• Expectation-Based Regression Detection - Stores expected test results and compares them against actual outcomes to detect regressions in CI.
• Reference Comparisons - Compares rendered web pages against reference pages to verify identical visual output.
• Rendering Tests - Verifies browser displays pages as expected by comparing rendered output against a reference.
• Shared Test Authoring - Writes tests that describe standard behavior in a machine-readable format so all browser projects can reuse them.
• Multi-Protocol Test Servers - Serves tests over HTTP, HTTPS, and WebSocket protocols using a single configurable server.
• Browser Automation Testing - Runs automated test suites against browsers using WebDriver and Python to verify standards compliance.
• Self-Contained HTML Test Pages - Loads self-contained HTML pages in any browser and checks whether they pass or fail based on programmatic or manual results.
• Automated Browser Launchers - Launches a specified browser automatically, loads test files, and collects results without manual interaction.
• Browser Execution - Starts local HTTP and WebSocket servers so tests can be loaded and executed interactively in a browser.
• Specification Conformance Validation - Automated system that checks browser implementations against W3C and WHATWG specifications using shared test cases.
• Browser Conformance Validators - Runs automated conformance tests against a browser to check whether its behavior matches web standards.
• Test Discovery Mechanisms - Discovers tests by scanning the filesystem and generating a manifest for efficient lookup and execution.
• Test Manifest Generators - Produces or updates a manifest file that indexes all available tests for efficient discovery and execution.
• Contribution Workflows - Submits test cases via pull requests with automatic labeling and reviewer notification, then reviews and merges contributions.
• Automated Reviewer Notification Systems - Automatically labels pull requests by changed directory and notifies relevant maintainers listed in META.yml files for streamlined peer review.
• Test Manifest Generators - Provides a manifest generator that enumerates all tests and their types for efficient discovery.
• Specification Discrepancy Reporting - Identifies discrepancies between browser behavior and web standards while authoring tests and reports findings to spec editors.
• Path-Based Reviewer Notifications - Automatically notifies maintainers by matching changed file paths against directory-specific META.yml files.
• Accessibility API Mapping Tests - Executes Python tests that check how browser accessibility APIs map to web content standards.
• Test Authoring - Tests browser automation behavior using Python and pytest to exercise the WebDriver protocol.
• Crashtests - Loads documents and passes if the browser completes without crashing.
• Test Report Exporters - Outputs test outcomes as human-readable logs or machine-readable JSON reports for debugging or upload.
• Branch-Triggered Full Runs - Triggers a full browser test run by pushing to a specially named branch and submits results to a dashboard.
• Custom Runner Implementations - Implements a tailored execution method for the test suite to support advanced or specialized workflows.
• Custom Test Runners - Provides a framework for implementing custom test runners that follow documented test-type behaviors.
• Cross-Browser Result Dashboards - Archives and displays test results collected from various browsers over time to monitor compatibility status.
• Human-Verified Pages - Creates pages requiring human interaction for verification when automation is not feasible.
• Specification Bug Discovery - Discovers discrepancies between browser implementations and standards during test authoring, feeding fixes back to spec editors.
• Test File Linters - Scans test files for common errors and style violations to maintain a consistent and correct test corpus.
• Testing Infrastructure and Management - Generates test manifests, lints test files, and manages TLS certificates to maintain a healthy test repository.
• Test Infrastructure - A hosted environment that enables running the full test suite from any browser without local setup or installation.
• Specification-Based Directory Structures - Structures test files under directories named after the web standard they cover, with subdirectories matching spec headings for larger specs.
• Visual Tests - Captures screenshots of rendered pages for comparison against expected renderings.
• Polyfill Injection Scripts - Injects a polyfill script into every test page so the polyfill's behavior can be verified across the suite.
• Polyfill Injection for Testing - Injects custom scripts into every test page to verify polyfill behavior across the full suite.
• Core Standards - Official cross-browser test suite for web platform features.
• Web Component Standards - Cross-browser test suite for web platform features and APIs.

سجل النجوم