Follow the steps mentioned here

pom.xml will also be created automatically. Afterwards you'll have to add required dependencies in it.

General guidelines:

• src/main/java contains your application code (.java files)

• src/main/resources contains any non-code files that go with your application. for instance property files or config files for your application (if they are not Java config files, like your config.xml).

• src/test/java contains any test code (.java files) for your application. If you mirror your package structure from src/main/java testing frameworks like Junit can automatically find the right classes to test without having to specify imports for them. In the case of Cucumber, this is where your step definitions go, as well as any other code that helps you perform your Cucumber tests (like the Page Objects in your example).

• src/test/resources contains any non code files that go with your tests. In the case of Cucumber, this is where the feature files go. If you have a separate test config.xml that would go here.

If you have only test code, you might not have a src/main folder. I'd recommend locating your test code in the same repository as the system you're going to test, as this will make it easier to get fast feedback.

Regarding your question:

1. Page Objects -> src/test/java

2. POJOs - depending on whether they are application POJOs or test POJOs -> src/main/java or src/test/java respectively

3. sharedutilities - asusming this is code to help your tests -> src/test/java

4. Feature Files -> src/test/resources

5. Config file -> depends on whether this is for the application or test, and whether its code or xml.

6. Expected Data folder - not sure what you mean. Test files (like .json or something) might go in src/test/resources

7. Extent config.xml - probably src/test/resources

8. chromedriver.exe - might go in your root directory. (I might recommend against including .exe in your project; how are you going to deal with different OS?)

9. Reports folder -> would probably go to a target folder?

Hope this helps.

I am not sure about the structure of your automation project. I prefer the following hierarchy in MAVEN projects

src
|-----main
|     |-----java
|           |-----Pages (contains application code arranged as one Class per Page)
|           |-----Steps (calls the page objects and methods called in Pages)
|-----test
      |------java
      |      |-----Test (Opens browser and calls steps to perform test - TestNG)
      |------resources
             |-----InputSheets
             |-----Environment Variables

The results are saved in C or D drive and are time stamped to avoid getting overwritten.

The automation helper library is created as a separate Maven project and is added as a dependency to the test project. In this way the helper library is independent from the test project and can be used across all projects if need arises.

All this being said, much of the structure is a matter of choice and varies according to your project requirements.