Skip to main content

Asset Smoke Testing

Summary​

This page describes what the asset-service smoke test covers and, importantly, what it does not prove. The smoke script drives the real asset lifecycle and asserts outbox rows, audit/timeline/outbox side-effects, and — with a notifications flag — a broker-free notification dispatch through the notification-service test path. Additional flags exercise workflow, documents, clearance, compatibility, gateway, backfill, parity, and cutover checks. It assumes a local database and sets a correlation id. No commands or environment details are reproduced here.

Audience​

  • QA engineers validating asset behavior locally.
  • Developers verifying changes before integration.
  • Support engineers understanding test coverage limits.

Reference Content​

What smoke covers​

The script drives the real lifecycle and asserts:

  • Outbox rows, including counts of events such as AssetAssigned and AssetRejected.
  • Audit, timeline, and outbox side-effects.
  • With a notifications flag, a broker-free notification dispatch through the notification-service test path.

Additional flags cover workflow, documents, clearance, compatibility, gateway, backfill, parity, and cutover checks.

Coverage map​

What smoke does NOT prove​

  • It does not prove broker delivery — the notification path is exercised broker-free through a test path.
  • It does not prove production readiness.
  • It assumes a local database and sets a correlation id; it is a local functional check, not an environment assurance.

Source References​

  • microservices/scripts/smoke-asset.ps1
  • microservices/src/asset-service/Api/AssetEndpoints.cs
  • microservices/src/asset-service/Api/AssetCompatEndpoints.cs

See Also​

Keywords​

asset smoke test, lifecycle assertions, coverage, broker-free, not production readiness

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-17
  • Review cycle: Quarterly