Ads

Maven Important terminologies

 Why Maven:

  • Can manage dependencies

  • to maintain proper project structure

  • used to create documentation

  • acts as build tool,compiler tool

Group id-company name

artifact -product

version-version

  1. Manage dependencies:

    1. once dependency added,required jars will be downloaded to the local automatically

  2. Maintain Code Structure:

    1. src/main/java-Actual code

    2. src/main/resources-UI related images,files stored here

    3. src/test/java-unit testing code

    4. src/test/resources--resources stored here against above test/java

    5. pom.xml-used to maintain dependencies,plugins,repositories

  3. acts as a build tool:

    1. maven compiler plugin used to maintain java 17 or to maintain required java version

    2. maven jar plugin used to convert the project into executable jar file-->main class has to be mentioned here

    3. maven dependency plugin also used to convert the project into executable jar file along with libraries

    4. right click on project--->run as-->maven build---goal as Package--->it will generate the executable file along with main class ,required librarires

  4. Maven working as a document tool

    1. if we give goal as site it will create a document in html file(professional documentation tool)

  5. Goals:

    1. default------>upto project deployment-------------->this lifecycle covers everything from validation to deployment

    2. clean--->delete target folder--->compiled code,packages will be removed

    3. site--->Document tool--->it shows test results,code coverage,project informations

    4. validate--->just check whether everything is correct like project name,pom.xml file is valid or not

    5. verify--->run check on results ensure quality--->post testing check

    6. package--->gives executable jar ,war,zip file

    7. test--->not package or deploy,it runs the test

    8. install--->installing or downloading the local dependencies in local

    9. deploy-->final stage deploying to central repository

Comments

Post a Comment

Popular posts from this blog

Rest Assured Api Automation

  1. What is Rest Assured, and why is it used? Answer: Rest Assured is a Java library used for testing RESTful APIs. It simplifies the process of sending HTTP requests, verifying responses, and automating API testing. Rest Assured provides a domain-specific language (DSL) for writing expressive tests, making it easier to test APIs without requiring extensive knowledge of HTTP. GEt method: RestAssured.BaseURI="https://jsonplaceholder.typicode.com/"; RequestSpecification reqSpec=RestAssured.given().accept(Contenttype.json).auth(). basicAuth("username","password").pathParam("sangar","kumar").header("Content-Type","application/json"); Response response=reqSpec.get("/sangar"); sysout(response.asString()); sysout(response.asPrettyString()); Assert.assertEquals(response.statusCode(),200,"Sangar bro"); Assert.assertTrue(response.statusMessage().contains("ok")); Post Method: Response response=Re...
Read more

Appium Notes

Image
  Appium is an open sourced mobile automation tool for testing navitive,hybrid,mobile app and browsers.. Appium internally uses WebDriver json wire protocol(which selenium does) to test the apps. Actually appium server acts as mediator between mobile application and Appium client libraries. Appium Client Libraries code is wrapping as json and sending to the appium server through json wire protocol.--->then appium server sending request to the mobile through UI Automator(kind of engine)--->automator response received by appium server and server sending response to the client libraries   Open image-20240905-071057.png Appium Architecture Appium is an open-source automation tool primarily designed for automating native, hybrid, and mobile web applications on iOS and Android platforms. Here's an overview of its architecture: Appium Server : Appium uses a client-server architecture. It listens for requests from clients (like Selenium WebDriver) and executes the commands on mo...
Read more

Jenkins Notes

  Continuous integration: once new commit is merged to the existing one, existing functionalities should not break.to ensure that for every commit, it is mandentory to run automated test for every new commit. this is called continuous integration.   New Item--->Free style project--->Enter name--->Free style---> General---> Description use custom workspace as project location---> Project is parameterised--->we can set the parameters and can be referred by %value% SourceCode--->Git along with credentials confuigured here--->once push done(this can be achieved by ngrok tunneling tool Build trigger--->usually we mention the schedule time data using cron time to configure automatic run. and we can set chain like depends on other project this will run Build steps-->we can add mvn test like command using windows batch command Post build actions-->we can configure email sending functions
Read more