You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Add comprehensive Vale integration test script to verify workflow functionality
- Create README with testing documentation and explanation
- Support local testing of Vale processing approach
- Simulate workflow environment for reliable validation
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
This directory contains utilities for testing the documentation validation workflows locally.
4
+
5
+
## Vale Testing
6
+
7
+
The `test-vale.sh` script is designed to validate that the Vale integration in the unified documentation workflow functions correctly. This script simulates the GitHub Actions environment and tests the full Vale style checking approach, including:
8
+
9
+
1. Installation of Vale using the same method as the workflow
10
+
2. Basic Vale execution and verification
11
+
3. JSON output format validation
12
+
4. Chunked processing of multiple files (as implemented in the workflow)
13
+
14
+
### Running the Test
15
+
16
+
To run the Vale integration test:
17
+
18
+
```bash
19
+
cd .github/docs/testing
20
+
./test-vale.sh
21
+
```
22
+
23
+
### What the Test Covers
24
+
25
+
- Validates that Vale can be properly installed and run
26
+
- Confirms that Vale produces valid JSON output
27
+
- Tests the chunked processing approach used in the workflow
28
+
- Verifies the JSON results combination logic
29
+
30
+
### When to Run This Test
31
+
32
+
Run this test when:
33
+
34
+
1. Making changes to the Vale integration in the docs-core action
35
+
2. Upgrading the Vale version used in the workflow
36
+
3. Modifying the Vale configuration or style rules
37
+
4. Troubleshooting Vale-related issues in the GitHub Actions environment
38
+
39
+
## Implementation Notes
40
+
41
+
The Vale integration in our workflow has two components:
42
+
43
+
1. Installation in the parent workflow (`docs-unified.yaml`)
44
+
2. Execution in the docs-core composite action
45
+
46
+
This approach ensures that Vale is properly installed and accessible to the composite action without requiring it to download and install Vale itself, which could be unreliable within the composite action context.
0 commit comments