A feature should be something you can verify.

All specific CondorAdmin capabilities remain pending verification. Concrete actions and failure cases provide a better evaluation than unsupported feature claims.

Access and action boundaries

Pending verification: how roles affect navigation, API access and record visibility, including server-side denial of unauthorized requests.

  • Compare access to the same record across roles
  • Check sessions after account suspension or permission removal
  • Inspect actor, target and result in audit records

Data and business states

Pending verification: consistent rules for creation, changes, approvals and deletion, including partial failure in batch work.

  • Try invalid input, repeated requests and concurrent operations
  • Align list, detail, export and reporting definitions
  • Check recovery, compensation and historical-data compatibility

Operations and delivery

Pending verification: executable documentation for runtime dependencies, configuration, migrations and backups.

  • Reproduce deployment and an upgrade in an isolated environment
  • Verify configuration-based secrets and redacted logs
  • Review health checks, diagnosis and rollback procedures

Interaction and accessibility

Pending verification: keyboard use, mobile viewports, language changes and errors across the core journey.

  • Read and complete essential tasks without animation
  • Check form labels, validation guidance and error focus
  • Keep equivalent content connected when switching languages