test: add test fixtures with sample payloads and config #195
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
thwap/ttheart!195
Loading…
Reference in a new issue
No description provided.
Delete branch "test/add-test-fixtures"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Add test fixtures in
test/testdata/:payload-push.json— push event with commits, repository, pusherpayload-issues.json— issue opened eventpayload-pull_request.json— PR opened eventpayload-release.json— release published eventpayload-check_suite.json— CI workflow completed eventconfig-all-rules.yamlexercising (#124):Why
Realistic test data for manual testing, integration tests, and the rule testing CLI. Payloads match actual Forgejo webhook structure.
Testing
go test ./...and pre-commit passBreaking Changes
None.
Closes #125
Closes #122
Closes #123
Closes #124
Review
Clean test fixtures. All JSON and YAML valid.
Payloads: 5 realistic Forgejo webhook payloads covering push, issues, pull_request, release, check_suite events. Each includes proper
repository,sender, and event-specific fields matching actual Forgejo format.Test config (
config-all-rules.yaml): 6 rules exercising all 5 condition operators (eq, ne, contains, matches, exists), all 3 template functions (json, timestamp, quote), timeout configuration, retry, and multiple actions per rule.ROADMAP.md: Updated.
No blocking issues.
APPROVED