Goal

Introduce an Ansible-based regression test suite to validate the core REST APIs after each milestone, bugfix, or feature merge — ensuring nothing is accidentally broken.

This will serve as a lightweight and modular test harness that can grow with the project.

Motivation

We want to verify (in a repeatable, automated fashion) that:

• Core entities (like roles and users) remain accessible
• Basic operations like create/delete/list continue to work after changes
• Future modules can be added easily, ideally one playbook per feature

Tasks

•  Create top-level Ansible playbook: verify.yml
•  Define roles:
  •  roles/api/verify_roles.yml: List and validate system roles
  •  roles/api/verify_users.yml: Fetch and validate known users (e.g., admin)
  •  roles/api/create_test_user.yml: Create a user rk with role FOO
  •  roles/api/delete_test_user.yml: Delete user rk and re-validate
•  Wire up each role into the top-level playbook
•  Make playbook fail cleanly if any call fails or yields unexpected response

Assumptions

• Backend runs locally at http://localhost:8080
• Uses the Ansible uri module to make REST calls
• Authentication is either open (for dev) or passed via basic auth/token

Stretch Goals

•  Integrate with a Git hook or CI step
•  Add support for checking response bodies (e.g., role names, user count)
•  Add support for future UI or gRPC tests (in a separate playbook)

Estimate

Initial setup (core roles + user CRUD): 2–3 hours

Adding additional playbooks for new features: 15–30 mins per feature