Device deletion tests depend on oneshot UIA

Open
#899 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
api, testing

Research direction

Start with the four referenced sections of tests/csapi/apidoc_device_management_test.go and compare their device-deletion setup with the context in related issue #893. Determine how the tests can exercise spec-compliant UIA rather than skipping it, then verify the device-management tests no longer rely on oneshot UIA or fail intermittently.

Written by the indexing model from the issue text.

Description

Dominant language
Go
Stars
100
Forks
72
Avg merge
4d 1h
Merged PRs (30d)
8

Contributor guide

Open the contributing guide

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 matrix-org/complement

All issues in matrix-org/complement

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.