Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

waitForIdle issue

Open
#164 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
desktop, testing

Research direction

Start by reading BasicRobot.waitForIdle and trace how it checks queues. Reproduce the A/B queue scenario described in the issue; done means waitForIdle does not report idle while work enqueued into another queue is still pending.

Written by the indexing model from the issue text.

Description

Given the method waitForIdle from the BasicRobot. It iterates through all queues and waits until the queue is cleared before moving to the next. But given a scenario with queues A and B. B is working.
Robot checks A. Robot checks B. Waits. B enqueues element in A. Robot checks B --> All queues cleared, though A is still working.

I have a possible solution in mind, let me know what you think.

Dominant language
Java
Stars
121
Forks
52
PR merge metrics
No merged PRs in 30d

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 assertj/assertj-swing

All issues in assertj/assertj-swing

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.