feat: per-test configuration for triggers and alerts

[metalwarrior665]

This will need some small changes in source actions but for repos, it is backward compatible

AI SUMMARY BELOW

Summary

This PR introduces a trigger-based test filtering system and alert configuration framework to the actor testing library. Tests and test suites can now be conditionally run based on trigger types (hourly, daily, pull request) and configured to send alerts to specific channels (Slack) when they fail.

Key Changes

• New trigger system (lib/trigger.ts):

  • getCurrentTrigger(): Reads the TEST_TRIGGER environment variable to determine the active trigger type
  • shouldRunForTrigger(): Evaluates whether a test should run based on its runWhen configuration and the current trigger
  • Supports three trigger types: hourly, daily, pullRequest

• Hierarchical trigger inheritance:

  • Added mergeInheritedTriggers() function that merges trigger configurations field-by-field through the describe hierarchy
  • Implements a trigger stack that tracks nested describe blocks, allowing child tests to inherit and override parent trigger settings
  • Both runWhen and alerts configurations are shallow-merged so children only need to override specific keys

• Updated describe() API:

  • Now accepts either a config object (DescribeConfig) or legacy string-based arguments
  • Config object supports name, triggers, and options properties
  • Maintains backward compatibility with existing string-based syntax
  • Pushes/pops triggers onto the stack during suite collection

• Updated testActor() and testStandbyActor() APIs:

  • Now accept either a config object (TestActorConfig) or legacy string-based arguments
  • Config object supports name, triggers, and options properties
  • Merges inherited triggers from enclosing describe blocks with test-level overrides
  • Embeds alerts configuration in task metadata for downstream processing by the report tool

• New type definitions (lib/types.ts):

  • TriggerType: Union of valid trigger types
  • RunWhenConfig: Controls which triggers enable a test
  • AlertsConfig: Defines alerting channels (currently Slack)
  • TriggerConfig: Combines runWhen and alerts
  • DescribeConfig and TestActorConfig: Configuration objects for the new API style
  • DescribeOptions and ActorOptions: Vitest-level test options

• Updated test reporting (bin/test-report.ts):

  • Reads alerts metadata from test results
  • Filters failed assertions by alert configuration (defaults to true for backward compatibility)
  • Only sends Slack notifications for assertions with alerts.slack !== false

• Comprehensive test coverage:

  • test/unit/triggers-merging.test.ts: Tests the trigger merging logic across various inheritance scenarios
  • test/unit/trigger.test.ts: Tests trigger detection and filtering logic

• Exported public API (index.ts):

  • Exports getCurrentTrigger() function
  • Exports new type definitions for trigger and alert configuration

Notable Implementation Details

• The trigger stack is maintained during vitest's synchronous suite collection phase, ensuring consistent state
• Trigger merging uses shallow object spread to allow field-by-field overrides without losing unspecified keys
• The system is backward-compatible: tests without trigger configuration run unconditionally, and the legacy string-based API is fully supported
• Alert configuration is embedded in task metadata so the JSON reporter can serialize it for downstream processing

https://claude.ai/code/session_01BHoLoyAPZsZB41xxysLagd

[ruocco-l]

Other than the pullRequest to be explicitly opt in, LGTM

[Patai5]

I trust the unit tests that were made by the LLM to do their job 😎

[metalwarrior665]

I have reverted the refactoring that moved some stuff to utils.ts, it was making the diff longer and making merging master harder. Let's do it later.

[metalwarrior665]

Corrected after merge conflicts. I will let it sit for a few days, then will do the last review, ping, and merge.