githubnext / githubnext/gh-aw-test

Suggested test: copilot/inline-engine-driver

Open
#9,240 0 comments 0 reactions 0 assignees View on GitHub
suggested new test
Dominant language
Shell
Stars
8
Forks
5
PR merge metrics
No merged PRs in 30d

Description

## Motivation

Link to the gh-aw PR: github/gh-aw#47991 — Add inline `engine.driver` sources for Copilot SDK workflows. The compiler now materializes inline Node, Python, Go, or Java driver sources at runtime from frontmatter, eliminating the need to commit a separate driver file.

## Proposed test

- **Workflow file**: `test-copilot-inline-engine-driver.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot (SDK mode with inline driver)
- **Safe output**: `create-issue`
- **Variant**: standard

## Minimal test prompt sketch

The workflow frontmatter declares a short inline TypeScript (Node) driver under `engine.driver.inline`. The driver calls the Copilot SDK to produce a `create-issue` safe output with a known title. The test verifies the issue is created, confirming that inline driver materialization and execution works end-to-end.

## New fixtures or secrets needed

None. An inline Node/TypeScript driver is self-contained and compiled at runtime by `gh aw compile`.

## Notes

No existing test exercises the inline `engine.driver` path — all current `copilot-*` tests use the default engine configuration. This is a net-new compiler feature deserving its own regression test. Should eventually be extended to Python and Go drivers, but one variant (Node/TypeScript) is sufficient for a first test.

> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/30196033978) · sonnet46 · 30 AIC · ⌖ 8.78 AIC · ⊞ 6.1K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-test+is%3Aissue+%22gh-aw-workflow-call-id%3A+githubnext%2Fgh-aw-test%2Fsuggest-new-e2e-tests%22&type=issues)

Contributor guide

No contributing guide indexed for this repository

Research direction

Create test-copilot-inline-engine-driver.md with a workflow_dispatch trigger and the inline Node/TypeScript driver described in the issue. Start by reading the existing copilot-* tests and the gh aw compile entry point; run the new workflow and confirm it produces the expected create-issue safe output without additional fixtures or secrets.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
testing-qa
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.