E2E Testing
CheckedHelps with AI, testing as part of testing, debugging, and quality assurance workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add ai-dashboad/flutter-skill --skill e2e-testing -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
ai-dashboad
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned ai-dashboad/flutter-skill at c31a08ead8.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- c31a08ead8
- Manifest
- skills/e2e-testing/SKILL.md
- Scanned
- 1 file, 157 lines
About this skill
What it does
This skill, E2E Testing, enables AI agents to interact with running applications across a variety of platforms using natural language commands. It provides an agent with the ability to see screenshots, tap elements, enter text, scroll, navigate, inspect UI trees, and verify application state—essentially giving the agent "eyes and hands" within the app. This allows for automated testing and debugging workflows without requiring any manual test code creation.
When to use it
- Testing user flows (e.g., login sequences, checkout processes) in applications.
- Debugging UI issues by having an agent interact with the application and verify expected behavior.
- Automating quality assurance tasks across different platforms.
- Verifying navigation and state changes within a running application.
- Exploring app functionality through natural language instructions.
Key capabilities
- Supports testing on Flutter (iOS/Android/Web), React Native, Electron, iOS (Swift/UIKit), Android (Kotlin), Tauri (Rust), KMP Desktop, and .NET MAUI platforms.
- Provides tools for taking screenshots (
screenshot). - Allows tapping elements by key, text, reference, or coordinates (
tap). - Enables entering text into fields (
enter_text). - Offers scrolling and swiping capabilities (
scroll,swipe). - Includes inspection tools to discover interactive elements (
inspect_interactive) and list all screen elements (get_elements). - Supports waiting for specific elements to appear (
wait_for_element).
Example prompts
- "Test the login flow — enter [email protected] and password123, tap Login, verify Dashboard appears."
- "Take a screenshot of the current screen and describe what's visible."
- "Scroll down to the bottom of the page and then tap the 'Submit' button."
Tips & gotchas
- Requires initial setup for each supported platform (e.g.,
flutter pub add flutter_skillfor Flutter). - The agent needs to be configured with the
flutter-skillMCP server details in its configuration. - You must first initialize your application using
flutter-skill init.