Problems while migrating from FEST 1.2 to AssertJ-Swing 3.17

Open
#257 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
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
desktop, testing

Research direction

Start by comparing the FEST 1.2 usages of JTabbedPaneFixture.selectedComponent() and ComponentFixture with the AssertJ-Swing 3.17 API. Verify whether AbstractComponentFixture is a supported replacement and document the supported migration path or workaround for both cases.

Written by the indexing model from the issue text.

Description

Hello,

there are two problems.

JTabbedPaneFixture tabbedPaneFixture = ...;
Component c = tabbedPaneFixture.selectedComponent();

The method call selectedComponent() doesn't work because it doesn't exist in the AssertJ-Swing 3.17. How can I solve it ? Or is there any work-around ?

ComponentFixture <?> cf = ...;
The class ComponentFixture is in FEST 1.2 but it doesn't exist in AssertJ-Swing 3.17.

Does it work by just replacing the ComponentFixture<?> with AbstractComponentFixture<?,?,?> ?

Thank you in advance.

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.