Merge pull request #20 from gripmock/snapshot-fix

fix snapshot

Author: rez1dent3

Cargo.toml

@@ -2,7 +2,7 @@
 resolver = "2"
 
 [workspace.package]
-version = "1.4.5"
+version = "1.4.6"
 edition = "2024"
 authors = ["bavix"]
 license = "MIT"

docs/advanced/index.md

@@ -15,7 +15,7 @@ grpctestify inspect test.gctf --format json
 grpctestify check tests/**/*.gctf
 
 # Format files
-grpctestify fmt -w tests/**/*.gctf
+grpctestify fmt -w .
 
 # Query server reflection
 grpctestify reflect package.Service/Method

docs/development/index.md

@@ -19,6 +19,18 @@ jobs:
         run: |
           brew tap gripmock/tap
           brew install gripmock/tap/grpctestify
+
+      # 1) Formatting gate (check mode, non-zero if reformat is needed)
+      - name: Check GCTF formatting
+        run: |
+          grpctestify fmt .
+
+      # 2) Syntax/semantic validation gate
+      - name: Validate GCTF files
+        run: |
+          grpctestify check .
+
+      # 3) Runtime execution gate
       - name: Run Tests
         run: |
           grpctestify tests/ --log-format junit --log-output results.xml
@@ -30,6 +42,15 @@ jobs:
           reporter: java-junit
 ```
 
+### Recommended CI order
+
+1. `grpctestify fmt <paths...>` - style/formatting check (fails if files need changes)
+2. `grpctestify check <paths...>` - parse + structural + semantic validation
+3. `grpctestify <paths...>` - real execution against gRPC service
+
+This split keeps failure causes explicit (style vs validation vs runtime)
+and mirrors common tooling workflows (`rustfmt --check` + linters/tests).
+
 ### Docker Integration
 
 ```dockerfile

docs/guides/getting-started/basic-concepts.md

@@ -31,7 +31,7 @@ package.Service/Method
 - `REQUEST_HEADERS` - request metadata
 - `TLS` - TLS/mTLS parameters
 - `PROTO` - descriptor/reflection configuration
-- `OPTIONS` - parsed and validated, currently not applied at runtime
+- `OPTIONS` - parsed, validated, and used for per-test runtime overrides (`timeout`, `retry`, `retry-delay`, `no-retry`)
 
 ## RPC patterns
 

docs/guides/reference/api/command-line.md

@@ -64,9 +64,20 @@ grpctestify tests/ --log-format junit --log-output test-results.xml
 grpctestify check tests/**/*.gctf
 
 # Format files in-place
-grpctestify fmt -w tests/**/*.gctf
+grpctestify fmt -w .
+
+# Check formatting (non-zero exit if changes are needed)
+grpctestify fmt .
 ```
 
+## Fmt Behavior
+
+- `grpctestify fmt <files...>` works as a formatting check and exits with code `1` if any file needs reformatting.
+- `grpctestify fmt -w <files...>` rewrites files in place.
+- Safe optimizer rewrites are applied by default during formatting.
+
+For CI, run both `fmt` and `check`: `fmt` enforces style, while `check` enforces parse/validation/semantics.
+
 ## See Also
 
 - [Test File Format](./test-files)

docs/guides/reference/api/grpc-default-test.md

@@ -46,5 +46,5 @@ grpctestify tests/ --verbose
 
 ## Notes
 
-- `OPTIONS` section is parsed but not applied at runtime
+- `OPTIONS` section can override per-test runtime flags (`timeout`, `retry`, `retry-delay`, `no-retry`)
 - `PROTO files=...` is not supported in native mode

docs/guides/reference/api/test-files.md

@@ -32,7 +32,7 @@ package.Service/Method
 - `REQUEST_HEADERS` (or `HEADERS`) - request metadata
 - `TLS` - TLS/mTLS config
 - `PROTO` - descriptor/reflection configuration
-- `OPTIONS` - parsed and validated, but currently not applied at runtime
+- `OPTIONS` - parsed, validated, and applied for per-test runtime overrides (`timeout`, `retry`, `retry-delay`, `no-retry`)
 
 ## Validation Rules
 

docs/guides/testing-patterns/data-validation.md

@@ -33,5 +33,5 @@ Use `RESPONSE` for strict matching or `ASSERTS` for flexible checks.
 
 Notes:
 
-- `OPTIONS` section is parsed but not applied at runtime
+- `OPTIONS` section supports runtime overrides (`timeout`, `retry`, `retry-delay`, `no-retry`)
 - Use `RESPONSE with_asserts=true` when you need both response match and assertions

docs/guides/testing-patterns/performance-testing.md

@@ -42,4 +42,4 @@ grpctestify tests/ --log-format junit --log-output perf-results.xml
 ## Notes
 
 - Use CLI flags for execution tuning
-- `OPTIONS` section is parsed but not currently applied at runtime
+- `OPTIONS` section can override per-test runtime behavior (`timeout`, `retry`, `retry-delay`, `no-retry`)

docs/guides/testing-patterns/testing-patterns.md

@@ -22,4 +22,4 @@ grpctestify tests/ --parallel 4 --timeout 30
 grpctestify tests/ --log-format json --log-output results.json
 ```
 
-Note: `OPTIONS` blocks are parsed but not applied at runtime.
+`OPTIONS` blocks support per-test overrides for `timeout`, `retry`, `retry-delay`, and `no-retry`.