From dbessono at openjdk.org  Wed Dec  3 16:14:29 2025
From: dbessono at openjdk.org (Dmitry Bessonov)
Date: Wed, 3 Dec 2025 16:14:29 GMT
Subject: RFR: 7904111: Feature Tests - Adding JavaTest GUI newly automated
 test scripts.
In-Reply-To: <w-dP6wD3qCOdjVLemOd7g2OSVWqDeACZc9uTTI-pQrM=.28cea480-6f56-40ef-9f47-873ac9a7de69@github.com>
References: <w-dP6wD3qCOdjVLemOd7g2OSVWqDeACZc9uTTI-pQrM=.28cea480-6f56-40ef-9f47-873ac9a7de69@github.com>
Message-ID: <dgYObUgIpoITmVEN-monoUmuDKrm5-xBa5LsMdRmThw=.b55ad56e-e482-48e9-bdf8-429185b634aa@github.com>

On Wed, 5 Nov 2025 13:32:26 GMT, Golla Yadav <duke at openjdk.org> wrote:

> Adding below automated newly JavaTest GUI feature Test Scripts to the Jemmy regression suite and tested locally on three platforms(Linux,Mac OS(JDK 1.8) and  Windows ) and working fine.
> 
> 1. ConfigEnvBrowser1.java
> 2. ConfigEnvBrowser2.java
> 3. ConfigEnvBrowser3.java

Should consistently use JUnit's Assert class instead of `assert`

gui-tests/src/gui/src/jthtest/ConfigEnvBrowser/ConfigEnvBrowser2.java line 77:

> 75:          Thread.sleep(3000);
> 76: 
> 77:          assert rowCount == 0 : "Test Failed: The Test Environment dialog should be displayed with no values.";

May we use JUnit's Assert class instead?

-------------

Changes requested by dbessono (Reviewer).

PR Review: https://git.openjdk.org/jtharness/pull/99#pullrequestreview-3535833915
PR Review Comment: https://git.openjdk.org/jtharness/pull/99#discussion_r2585743387