Maven Features and Advantages

Lets Kode It
A free video tutorial from Lets Kode It
Anyone can code - Changing Lives Everyday
4.5 instructor rating • 8 courses • 87,279 students

Lecture description

You will learn about features and advantages of using Maven

Learn more from the full course

Selenium WebDriver With Java - Novice To Ninja + Interview

Join the "Top Rated #1 Best Selenium Course"-Basics To Advanced Level With POM, Grid, Maven, GitHub, Jenkins, Interviews

43:34:03 of on-demand video • Updated August 2020

  • ***** At the end of this course, you will have detailed understanding of Web Automation Frameworks
  • You will be able to EXPLAIN, DESIGN and IMPLEMENT structured AUTOMATION FRAMEWORKS using Page Object/Factory Model
  • *** In-depth understanding of Selenium WebDriver CHALLENGES with real time examples
  • You will be able to implement CONTINUOUS INTEGRATION TESTING using JENKINS
  • ***** We have 10 dedicated INSTRUCTORS to help you with queries within 24 HOURS, resume preparation, Interview questions
  • You will be able to perform CROSS-BROWSER testing using SELENIUM GRID
  • You will be able to create GREAT LOOKING REPORTS using the best advanced REPORTING TOOL
  • You will have complete understanding of TestNG Framework
  • ***** You will have excellent command on Build Management using MAVEN
  • ***** You should be able to lead any Selenium Automation Project from scratch on your own
  • ***** You will have understanding of Behavior Driven Testing Using CUCUMBER, Gherkin language
  • ***** You will be able to understand and write efficient testing code
  • You will have required skills to automate any web application
  • You should be able to verify Data Integrity with the GUI of the application
  • Additional Knowledge of running Performance tests with Selenium WebDriver Automation
  • With all this knowledge gained, you should be easily able to clear Selenium Automation interviews
English Hello Guys welcome back to the next tutorial. And this one we're going to talk about May 1 and start what Maven is what how it's going to help and what we're going to learn in the tutorial from here. So there was going to be a series of lectures about maybe five or six in which we're going to study different topics. So I'm just going to go over what we're going to learn and just keep it simple in our way. So let's get started. It's going to be short and small. So I just was like for you guys. So since May 1 What is May 1. So when it's just a simple software project management tool it helps us sort of managing products belt's reporting documentation from just one piece of information and one central piece all the information is calibrated and one central space so it creates a project hierarchy for us. We can actually do that manually as well. So it creates segregation between different types of classes that devlopment classes in the test and all those things. So what we usually do is create different packages for four different pages different classes utilities and test ride. That's what we always do. So one may wonder this movement helps us in achieving. I think it creates a decent project Haokip for us. We're in one project we can have project classes and then there's going to be a test hierarchy. So in that package we can have our test classes. So that sort of thing that may win helps us and do those sort of things. So what is the objective of me. And so what maven does is it makes the whole process easy. So this is this is these are straight up from the once official website where one may 20th what is its objectives. So what it does is it helps us in making the process easy. What does it mean. So it doesn't eliminate the need to know every underlying mechanism but what it provides is a lot of shielding from the details. So we don't need to know a lot of things that that's going inside the beltway stumble process or what but what we can do is configure everything from day one and it runs very smoothly and then for a creator it's really easy. So that's number one objective advantage all you can see that. So the next thing is providing a uniform rail system. Right. So I mean when does is it allows a project to build using its palm which is the Project Object Model . So that's that's something that me when you was asked to build its projects and will cover what part is in detail. So because of that and it allows us you're building a project using dad and Assaraf against that are shared by all the project. So what happens is there is a common and uniform Bell System and it follows everything based on the farm. So once you understand them may when you will actually realize how this saves a lot of time in building and that getting too many projects because they all pretty much follow the same thing. If if a project is me when implemented then they are all seem they're following the same hierarchy. So it's really easy to build them and to navigate them navigate through them to understand where my files could be. So it's a very good uniform practice. The next thing is providing quality project information. So one provides plenty of useful product information that is in part sort of taken from your palm file and generated from the project sources. So for example it can turn the changelog documents from you. And those are created directly from the source control. It can get you the mailing list and it can you can provide the dependency list or dependencies are the char files with on which we depend on to run a project. Right. So it can provide us unit test reporting also. So if you remember when we created a project we added the selenium jar file to the log Faraji log for the tar files and the test changed our files to the project rates. So those are the dependencies so one me won't provide us in the palm file we can mention those dependencies and it does the job for us. We don't have to explicitly download the char files in our computer and then associate them with the project. So that's something that me one does it for us we just need to specify what we need. So that's pretty interesting and you'll see that how it happens that providing guidelines for best practices . So me one sort of aims to gather current principles for best practice devlopment and then it makes it easy to guide a project in that direction. Right. So let's say there are specifications exclusions and sort of coverage unit coverage of unit tests that they're all part of the normal build cycle using me. So what how it helps is like keeping your test source code in a separate and. But the parallels or stories so as I was mentioning it helps define the hierarchy of a project. So we're going to have a main project which is a development project and then there's going to be that's a folder and inside that's going to be different packages for that development. So in a similar segregated folder which is just inside the same project we can have a test folder in which there's again going to be different packages for test classes and they're all going to have to share the same sort of naming conventions so it's easy to identify which class is the test class for which Development class. So it's pretty easy because using that same test case naming convention we know where to locate and execute tests and have test cases set up there and I may even also sort of suggest some guidelines on how doolally lay out your project characteristics. That's what I was already talking about. So it helped us in getting the decent project hierarchy. So the second and so sort of next thing is I like transparent migration new features. So it just nothings. But it's easy for me and clients to update their installation so they can it take they bind pages when there is something change in. So let's say an new version of me when it comes in from maybe 3.0 will keep buying one or something else. So it sort of provides a really easy migration. So it's really easy to do that too. So maybe is when we are using it for the current version it's a easy win and we need upgrades and we want to upgrade it to the latest word. It's really easy. So it's pretty small. That's that's one really great thing. So what's in there. So what's in the tutorial are we going to cower when we talk about may well of those things. So we'll talk about the advantages that we were just now talking about advantages and features. And in the next tutorial we're going to talk about Mame and set up a central repository of May 1. How do we create a May one project and then we'll talk about understanding. I mean these are not in a particular order but will we're going to talk about all those things separately and then we're going to talk about understanding Pomme. So that's the sort of core of the me one where everything they say. And once we understand this we're done. I mean we're pretty much done with me and we know what we have to do in May and we'll talk about dependencies which is actually sort of a part of Parmalat like XML. So you might not even think of a different topic we might include in the same lecture and we're going to talk about testing the integration side of and Jenkin's integration sort of how we have written our test right now till falling on Armel project Anderson. So we'll try to convert all of them into maybe one project. So we'll talk about those things. So that should be our sort of things that we need to do. And that's pretty much it. So I think that that's premature for this lecture. And I would say I mean there's nothing to practice so I would say just go about go through some documents and if you wish to and stadium for the next lictors guys and just keep watching and thanks for ending this one. Thank you so much guys.