7903177: Feature Tests - Adding five JavaTest GUI legacy automated test scripts

[gollayadav]

Adding below automated legacy JavaTest GUI feature Test Scripts to the Jemmy regression suite and tested locally on three platforms(Linux, Windows, Mac OS) and working fine.

1.Config_Load5.java
2.Config_Load6.java
3.Config_LoadEdit1.java
4.Config_LoadEdit2.java
5.Config_LoadEdit3.java

---

Progress

• Change must not contain extraneous whitespace

Issue

• CODETOOLS-7903177: Feature Tests - Adding five JavaTest GUI legacy automated test scripts

Reviewers

• Dmitry Bessonov (@dbessono - Committer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jtharness pull/29/head:pull/29
$ git checkout pull/29

Update a local copy of the PR:
$ git checkout pull/29
$ git pull https://git.openjdk.java.net/jtharness pull/29/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 29

View PR using the GUI difftool:
$ git pr show -t 29

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jtharness/pull/29.diff

[bridgekeeper]

👋 Welcome back gollayadav! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@gollayadav This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

7903177: Feature Tests - Adding five JavaTest GUI legacy automated test scripts

Reviewed-by: dbessono

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 1 new commit pushed to the master branch:

• 036dae1: 7903170: Sanity Tests - Adding JavaTest GUI newly automated test scripts

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@dbessono) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[mlbridge]

Webrevs

• 02: Full - Incremental (0634d251)
• 01: Full - Incremental (643abae1)
• 00: Full (746ce60d)

[dbessono]

This looks not correct. Instead it would be better to have a short description of what the test is doing.

[dbessono]

looks not correct, could be removed

[dbessono]

looks not correct

[dbessono]

Please remove this

[gollayadav]

Thank You for your time in reviewing. I have updated/modified the scripts as per the review comments. Could you please check.

[dbessono]

During the first iteration missed that this test is empty. It it really needed at all?

[gollayadav]

Verified that this empty test script is not required and removing it.

[dbessono]

What is the purpose of this test?

/**
 *This tests verifies the load button under configuration editor
 */
public class Config_LoadEdit extends ConfigTools {

}

[dbessono]

Thank you for the updates, looking good

[gollayadav]

/integrate

[dbessono]

/sponsor

[openjdk]

@gollayadav
Your change (at version 0634d25) is now ready to be sponsored by a Committer.

[openjdk]

Going to push as commit 4c0a9ad.
Since your change was applied there has been 1 commit pushed to the master branch:

• 036dae1: 7903170: Sanity Tests - Adding JavaTest GUI newly automated test scripts

Your commit was automatically rebased without conflicts.

[openjdk]

@dbessono @gollayadav Pushed as commit 4c0a9ad.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.