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

Notification about further migration steps I encountered

Open
#267 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
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
documentation

Research direction

Start with the AssertJ Swing migration guide linked in the issue and compare its existing migration steps with the four reported API changes. Document these replacements in the guide, then verify that all four migration steps are clearly stated for users upgrading from fest-swing 1.2 to assertj-swing-junit 3.17.1.

Written by the indexing model from the issue text.

Description

In response to

please don't hesitate to notify us about further migration steps you encounter!
Source: https://joel-costigliola.github.io/assertj/assertj-swing-migrating.html

Here are the four additional steps I had to perform when upgrading from org.easytesting:fest-swing:1.2 to org.assertj:assertj-swing-junit:3.17.1:

  • org.fest.swing.driver.JTableCellValidator.validateCellIndices was renamed to org.assertj.swing.driver.JTableCellPreconditions.checkCellIndicesInBounds
  • org.fest.swing.query.ComponentBackgroundQuery.backgroundOf(component) had to be replaced with org.assertj.swing.edt.GuiActionRunner.execute(() -> component.getBackground())
  • org.fest.swing.query.ComponentFontQuery.fontOf(component) had to be replaced with org.assertj.swing.edt.GuiActionRunner.execute(() -> component.getFont())
  • org.fest.swing.query.ComponentForegroundQuery.foregroundOf(component) had to be replaced with org.assertj.swing.edt.GuiActionRunner.execute(() -> component.getForeground())
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.