Skip to content

Source truth: - Vision and Product Principles - Company Identity and Context Contract - Financial Period Contract - Journal Entry Contract - Actor Identity Contract - Roles and Permissions Contract - Protected Actions Contract - Security Audit Event Contract - Business Time Contract

Testing

This page explains testing practices for accounting behavior.

  • Test canonical rules explicitly.
  • Test named-zone validation and period cutoff resolution across standard time, daylight-saving time, and invalid or ambiguous local boundaries. Assert that user or host zones cannot change company period membership.
  • Validate period status transitions and posting behavior.
  • Keep audit trail and correction flows covered.
  • For chart of accounts behavior, test immutable account identity, code uniqueness, code resolution, role cardinality, account history, starter chart idempotency, and import validation.

Developer test identity

Automated and manual development tests may use the seeded Developer Test User in BooksPlus Test Company.

This actor and company must use ordinary company-context, authorization, and audit behavior. They must not bypass protected-action policy checks.

Required coverage:

  • development/test seeding creates or resolves the persisted BooksPlus Test Company, Developer Test User, and Developer Test Full Access;
  • BooksPlus Test Company has stable company identity and is unavailable in production mode unless explicit development or test mode is active;
  • the developer test bundle covers every registered protected action;
  • the developer test actor can execute protected happy paths through normal policy checks;
  • a narrower actor without the required permission is denied;
  • a disabled or retired developer test actor is denied;
  • protected actions emit audit events with actor identifier, company identifier, action, result, and correlation context when available;
  • production mode does not create or activate the developer test company, actor, or permission bundle.