test(integration): Add a Bruno request for Revoke Other Sessions (POST /v1/auth/sessions/revoke-others) to the api-tests collection

Open Beginner friendly
#699 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
testing

Research direction

Read the Bruno request style in api-tests/Whitelist/Get Config.bru and the api-tests/README.md; check crates/api/src/lib.rs for the revoke-others route. Add api-tests/Sessions/Revoke Other Sessions.bru using the named environment variables, saving the replacement token and asserting the expected status. Run the request against a local server and update the README; done when the request passes and the documented collection includes it.

Written by the indexing model from the issue text.

Description

area/integration area/testing enhancement good first issue help wanted

Description

The Bruno collection under api-tests/ has no request for POST /v1/auth/sessions/revoke-others, although the route exists in crates/api/src/lib.rs.

Requirements and context

  • Where: api-tests/Sessions/, api-tests/README.md
  • Security: Use only test accounts and environment variables; no real tokens in the repo.
  • Testing: just fmt-check, just lint and just test must pass; add or update tests for the change.
  • Documentation: Update the nearest doc if behaviour changes; otherwise no doc change is needed.

Suggested execution

  • Comment on this issue to claim it, then fork the repository and branch from main.
  • Branch name: git checkout -b test/bruno-sessions-revoke-others

Implement changes

  • Add Revoke Other Sessions.bru under api-tests/Sessions/ following the style of api-tests/Whitelist/Get Config.bru. It returns a replacement token, so save it into the token variable.
  • Use {{base_url}}, {{token}} and {{wallet_id}} variables; never hard-code credentials.
  • Add a short tests {} assertion for the expected status code and mention it in api-tests/README.md.

Test and commit

  • Run the request with Bruno against a local server (just run) or bru run and confirm it passes.
  • Run just fmt, just lint and just test locally before pushing (see CONTRIBUTING.md).
  • Commit with a conventional message and keep the change small and focused.

Example commit message

test(integration): add bruno request for sessions-revoke-others

Guidelines

  • Open the PR against main and link it with Closes #<this issue>.
  • Keep the diff focused on this issue; no unrelated refactors or formatting churn.
  • One line per comment, no bloated code; follow patterns already used in the crate.
  • Never commit secrets, .env files or real keys; use public test vectors only.
  • CI (fmt, clippy -D warnings, tests) must be green before requesting review.
  • Ask in the issue thread if anything is unclear before starting.
Dominant language
Rust
Stars
0
Forks
91
Avg merge
5h 23m
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Octo-Protocol-org/Octo-Protocol

All issues in Octo-Protocol-org/Octo-Protocol

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.