Skip to main content
Glama

flutter_test

Execute Flutter tests and generate coverage reports to verify mobile application functionality and code quality.

Instructions

Run Flutter tests with optional coverage

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdYesWorking directory (Flutter project root)
testFileNoSpecific test file to run (optional)
coverageNoEnable test coverage

Implementation Reference

  • Executes the flutter_test tool: validates input, checks Flutter project and test file, runs 'flutter test' command with optional coverage, returns results with pass/fail status.
      handler: async (args: any) => {
        const validation = FlutterTestSchema.safeParse(args);
        if (!validation.success) {
          throw new Error(`Invalid request: ${validation.error.message}`);
        }
    
        const { cwd, testFile, coverage = false } = validation.data;
    
        // Validate that it's a Flutter project
        await validateFlutterProject(cwd);
    
        const flutter_args = ['test'];
        
        if (testFile) {
          // Validate test file path (must be .dart file in test directory)
          if (!testFile.endsWith('.dart')) {
            throw new Error(`Test file must be a .dart file. Invalid test file: ${testFile}`);
          }
          
          // Check if test file exists
          const testFilePath = path.isAbsolute(testFile) ? testFile : path.join(cwd, testFile);
          try {
            await fs.access(testFilePath);
          } catch {
            throw new Error(`Test file not found. File does not exist: ${testFilePath}`);
          }
          
          flutter_args.push(testFile);
        }
        
        if (coverage) {
          flutter_args.push('--coverage');
        }
    
        const result = await processExecutor.execute('flutter', flutter_args, {
          cwd,
          timeout: 600000, // 10 minutes timeout for tests
        });
    
        return {
          success: true,
          data: {
            testFile: testFile || 'all tests',
            coverage,
            projectPath: cwd,
            exitCode: result.exitCode,
            output: result.stdout,
            errors: result.stderr,
            duration: result.duration,
            passed: result.exitCode === 0,
          },
        };
      }
    });
  • Zod validation schema for flutter_test tool inputs: project directory (cwd), optional test file, and coverage flag.
    const FlutterTestSchema = z.object({
      cwd: z.string().min(1),
      testFile: z.string().optional(),
      coverage: z.boolean().default(false),
    });
  • Registers the flutter_test tool in the tools map within createFlutterTools function, defining name, description, JSON inputSchema, and handler.
    tools.set('flutter_test', {
      name: 'flutter_test',
      description: 'Run Flutter tests with optional coverage',
      inputSchema: {
        type: 'object',
        properties: {
          cwd: { type: 'string', minLength: 1, description: 'Working directory (Flutter project root)' },
          testFile: { type: 'string', description: 'Specific test file to run (optional)' },
          coverage: { type: 'boolean', description: 'Enable test coverage' }
        },
        required: ['cwd']
      },
      handler: async (args: any) => {
        const validation = FlutterTestSchema.safeParse(args);
        if (!validation.success) {
          throw new Error(`Invalid request: ${validation.error.message}`);
        }
    
        const { cwd, testFile, coverage = false } = validation.data;
    
        // Validate that it's a Flutter project
        await validateFlutterProject(cwd);
    
        const flutter_args = ['test'];
        
        if (testFile) {
          // Validate test file path (must be .dart file in test directory)
          if (!testFile.endsWith('.dart')) {
            throw new Error(`Test file must be a .dart file. Invalid test file: ${testFile}`);
          }
          
          // Check if test file exists
          const testFilePath = path.isAbsolute(testFile) ? testFile : path.join(cwd, testFile);
          try {
            await fs.access(testFilePath);
          } catch {
            throw new Error(`Test file not found. File does not exist: ${testFilePath}`);
          }
          
          flutter_args.push(testFile);
        }
        
        if (coverage) {
          flutter_args.push('--coverage');
        }
    
        const result = await processExecutor.execute('flutter', flutter_args, {
          cwd,
          timeout: 600000, // 10 minutes timeout for tests
        });
    
        return {
          success: true,
          data: {
            testFile: testFile || 'all tests',
            coverage,
            projectPath: cwd,
            exitCode: result.exitCode,
            output: result.stdout,
            errors: result.stderr,
            duration: result.duration,
            passed: result.exitCode === 0,
          },
        };
      }
    });
  • TypeScript type definition and Zod schema export for FlutterTest inputs (slightly variant).
    export const FlutterTestSchema = z.object({
      cwd: z.string(),
      testFile: z.string().optional(),
      coverage: z.boolean().optional(),
    });
  • Helper function to validate that the given directory is a valid Flutter project by checking pubspec.yaml presence and flutter section.
    const validateFlutterProject = async (cwd: string): Promise<void> => {
      const pubspecPath = path.join(cwd, 'pubspec.yaml');
      try {
        await fs.access(pubspecPath);
        const pubspecContent = await fs.readFile(pubspecPath, 'utf8');
        if (!pubspecContent.includes('flutter:')) {
          throw new Error(`Directory does not appear to be a Flutter project. No flutter section found in ${pubspecPath}`);
        }
      } catch {
        throw new Error(`pubspec.yaml not found. Flutter project must contain pubspec.yaml at: ${pubspecPath}`);
      }
    };
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions running tests with optional coverage but lacks details on execution behavior (e.g., output format, error handling, or dependencies like Flutter SDK). This is insufficient for a tool with potential side effects like test execution.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose ('Run Flutter tests') and adds a useful qualifier ('with optional coverage'). There is no wasted verbiage, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what happens during test execution, what outputs or errors to expect, or how it interacts with other tools like 'flutter_test_suite'. For a tool that runs tests, more context is needed for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so parameters are well-documented in the schema. The description adds no additional semantic context beyond implying coverage is optional, which is already covered by the schema. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Run Flutter tests') and resource ('Flutter tests'), with an optional feature ('with optional coverage'). It distinguishes from siblings like 'flutter_test_suite' by focusing on running tests rather than managing test suites, though the distinction could be more explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as 'flutter_test_suite' or other testing-related tools. The description mentions coverage as optional but doesn't specify scenarios or prerequisites for usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cristianoaredes/mcp-mobile-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server