mirror of
https://github.com/Z3Prover/z3
synced 2026-02-03 15:56:17 +00:00
Enable ad-hoc deeptest workflow execution via workflow_dispatch (#8448)
* Initial plan * Remove slash_command and blocking activation conditions from deeptest workflow - Remove slash_command configuration to eliminate team membership and command position checks - Simplify workflow to only support workflow_dispatch for ad-hoc execution - Remove pre_activation job and complex activation conditions - Update README to reflect workflow_dispatch-only usage - Keep file_path input parameter for specifying source files to test Co-authored-by: NikolajBjorner <3085284+NikolajBjorner@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: NikolajBjorner <3085284+NikolajBjorner@users.noreply.github.com>
This commit is contained in:
parent
10043c37fd
commit
74cbd6de32
3 changed files with 26 additions and 166 deletions
29
.github/workflows/README-deeptest.md
vendored
29
.github/workflows/README-deeptest.md
vendored
|
|
@ -15,7 +15,7 @@ DeepTest is an AI-powered GitHub Agentic Workflow that automatically generates c
|
|||
|
||||
## How to Use
|
||||
|
||||
### Method 1: Workflow Dispatch (Manual Trigger)
|
||||
### Workflow Dispatch (Manual Trigger)
|
||||
|
||||
1. Go to **Actions** → **Deeptest** in the GitHub repository
|
||||
2. Click **Run workflow**
|
||||
|
|
@ -23,20 +23,11 @@ DeepTest is an AI-powered GitHub Agentic Workflow that automatically generates c
|
|||
4. Optionally link to an issue number
|
||||
5. Click **Run workflow**
|
||||
|
||||
### Method 2: Slash Command (In Issues/PRs)
|
||||
|
||||
Simply comment on any issue or pull request:
|
||||
|
||||
```
|
||||
/deeptest src/util/vector.h
|
||||
```
|
||||
|
||||
The workflow will:
|
||||
1. Extract the file path from your comment
|
||||
2. Analyze the source file
|
||||
3. Generate comprehensive tests
|
||||
4. Create a pull request with the test files
|
||||
5. Add a comment with statistics and instructions
|
||||
1. Analyze the source file
|
||||
2. Generate comprehensive tests
|
||||
3. Create a pull request with the test files
|
||||
4. Optionally add a comment to the linked issue with statistics and instructions
|
||||
|
||||
## What Gets Generated
|
||||
|
||||
|
|
@ -83,16 +74,12 @@ After running, DeepTest will:
|
|||
## Example Usage
|
||||
|
||||
### Example 1: Test a C++ utility file
|
||||
```
|
||||
/deeptest src/util/vector.h
|
||||
```
|
||||
Via workflow dispatch with file path: `src/util/vector.h`
|
||||
|
||||
### Example 2: Test a Python API file
|
||||
```
|
||||
/deeptest src/api/python/z3/z3.py
|
||||
```
|
||||
Via workflow dispatch with file path: `src/api/python/z3/z3.py`
|
||||
|
||||
### Example 3: Via workflow dispatch
|
||||
### Example 3: Link to an issue
|
||||
- File path: `src/ast/ast.cpp`
|
||||
- Issue number: `1234` (optional)
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue