********************************************************************** Thanks for watching: Launch your learning --- 🚀🚀🚀🚀🚀🚀🚀 This course is easy step by step approach to build a practical Java based Selenium framework in Intellij. This covers in almost 2 hours various topics like how to setup java, maven in local machine as well testng & selenium dependency in the Project. This course has avoided traditional Java IDE eclipse and focussed on latest Intellij IDEA IDE which are being used in enterprise solutions. cover various topics like TestNG framework, Page Object Model concept, with emphasis on Extent reporting and Jenkins integrations ********************************************************************** 00:02:00: listing step by step for the course 00:03:55: Installation of Intellij Idea in local machine 00:07:33: Verify java in local machine ( If not there then installation steps) & setting up of system & environment variables 00:16:06: Verify Maven in local machine ( If not there then installation steps) & setting up of system & environment variables 00:23:09: Create a Maven Project and add TestNG dependency 00:27:27: Add Selenium web driver dependency, Install & add chrome web driver in the project. 00:37:30: Look at our Application under test and the 2-3 testcases that we have to automate 00:40:30: Brief look at Page object model concept & advantages of using Page object model (for reusability) 00:42:03: Capture the web page element properties inside the page object classes ( after creating Pages folder) 01:00:39: Adding the TestNg Annotations @BeforeSuite for launching the browser 01:03:33: Initializing the chrome driver method 01:07:56: Adding the Page Object methods to perform operations 01:09:52: Adding the Test Annotations 01:16:51: Adding asserts inside the Page Object methods 01:21:31: Extent Reporting advantages 01:29:56: Searching and adding the extent report dependency 01:34:00: Adding the details of the Extent report variables and methods 01:41:11: Verifying the extent html report 01:58:16: Verifying the results of test execution in the piechart format 01:56:21: example of how failure of a testcase appears on the extent report 01:58:21: capturing screenshots in our test automation framework 02:04:43: pushing the code from local to github repository 02:05:49: Jenkins in local machine : enter the credentials 02:06:35: Creating a new jenkins job to configure the jenkins pipeline 02:08:45: Building the jenkins job 02:10:09: Adding the Publish html report 02:11:07: verifying the extent report on the jenkins job run
@@aceautomationacademy6926 oh I fixed it. Thank you for the response. I had gotten my hamburger_menu xpath wrong at the end "/input" was omitted. With Thread.sleep I had to add "throws InterruptionExce.." to the first test case(validateTitles).
Hi Mohammed, Java 11 is just an example. Ofcourse framework design will remain the same, the versions of libraries may change. Let me know incase you wanted specific to Java 21 version
@@aceautomationacademy6926 Thanks for your time. Yes, we know that's just an example, but why don't doing an example with newer versions, we're in 2024 man
@truck.-kun. If it doesn't matter and there is no difference so use the newest, today there is no difference but tomorrow you will have difference and compatibility problems, if you are in 2024 use the latest lte which is Java 21.
Why exactly are you adding the drivers when selenium 4.0 onwards it takes care of it automatically? Also, those xpaths are one of the most horrible things I’ve seen. You have absolute xpaths everywhere, change the code. It’s terrible.
Hi Ameya Godse: your point is valid - the xpaths used in this video are absolute xpaths and not relative xpaths. other point is related to chrome drivers - intention of this video was quick setup of framework and focus on couple of requests that came i.e: how to do reusability of methods in variety of testcases, extent reports, jenkins integration as mentioned in introduction. sure - will prepare on the focus area of xpaths and webdriver manager.
FreeMarker template error: Template inclusion failed (for parameter value "partials/exceptıon.ftl"): Template not found for name "spark/partials/exceptıon.ftl". The name was interpreted by this TemplateLoader: ClassTemplateLoader(resourceLoaderClass=com.aventstack.extentreports.ExtentReports, basePackagePath="templates/" /* relatively to resourceLoaderClass pkg */). Why does it give such an error, what is the solution?
**********************************************************************
Thanks for watching: Launch your learning --- 🚀🚀🚀🚀🚀🚀🚀
This course is easy step by step approach to build a practical Java based Selenium framework in Intellij.
This covers in almost 2 hours various topics like how to setup java, maven in local machine as well testng & selenium dependency in the Project. This course has avoided traditional Java IDE eclipse and focussed on latest Intellij IDEA IDE which are being used in enterprise solutions.
cover various topics like TestNG framework, Page Object Model concept, with emphasis on Extent reporting and Jenkins integrations
**********************************************************************
00:02:00: listing step by step for the course
00:03:55: Installation of Intellij Idea in local machine
00:07:33: Verify java in local machine ( If not there then installation steps) & setting up of system & environment variables
00:16:06: Verify Maven in local machine ( If not there then installation steps) & setting up of system & environment variables
00:23:09: Create a Maven Project and add TestNG dependency
00:27:27: Add Selenium web driver dependency, Install & add chrome web driver in the project.
00:37:30: Look at our Application under test and the 2-3 testcases that we have to automate
00:40:30: Brief look at Page object model concept & advantages of using Page object model (for reusability)
00:42:03: Capture the web page element properties inside the page object classes ( after creating Pages folder)
01:00:39: Adding the TestNg Annotations @BeforeSuite for launching the browser
01:03:33: Initializing the chrome driver method
01:07:56: Adding the Page Object methods to perform operations
01:09:52: Adding the Test Annotations
01:16:51: Adding asserts inside the Page Object methods
01:21:31: Extent Reporting advantages
01:29:56: Searching and adding the extent report dependency
01:34:00: Adding the details of the Extent report variables and methods
01:41:11: Verifying the extent html report
01:58:16: Verifying the results of test execution in the piechart format
01:56:21: example of how failure of a testcase appears on the extent report
01:58:21: capturing screenshots in our test automation framework
02:04:43: pushing the code from local to github repository
02:05:49: Jenkins in local machine : enter the credentials
02:06:35: Creating a new jenkins job to configure the jenkins pipeline
02:08:45: Building the jenkins job
02:10:09: Adding the Publish html report
02:11:07: verifying the extent report on the jenkins job run
Thanks for providing this tutorial! It's helpful!
Glad it was helpful!
I Love it. FINALLY!!! I found updated and clear video about testng
Excellent explanation thank you so much 😊 please keep it coming thanks again .
The way you are explaining it's really amazing, i never ever seen this kind of explanation, thank you so much ❤
Thank you for the tutorial! 💯
Thanks rowel
Very useful 🙏 thanks❤
Thanks atul
Thank you for the tutorial! please share GITHUB code URL all session videos.
correct me if im wrong - instead of installing chrome driver we can add webdriver manager dependency rit?
hi Syed - you are right yes we can add webdriver manager dependency as well to manage browser driver versions
Hi, i hope you're good. So when it fomes to thread.sleep mine keeps saying there's a relative problem. Is there another way to do it or get around it
Hi Austin, am doing good thanks, could you provide the full error message
@@aceautomationacademy6926 oh I fixed it. Thank you for the response. I had gotten my hamburger_menu xpath wrong at the end "/input" was omitted. With Thread.sleep I had to add "throws InterruptionExce.." to the first test case(validateTitles).
I don't know why you all continue using java 11 instead of newer version like java 21 lts
Hi Mohammed, Java 11 is just an example.
Ofcourse framework design will remain the same, the versions of libraries may change. Let me know incase you wanted specific to Java 21 version
@@aceautomationacademy6926
Thanks for your time.
Yes, we know that's just an example, but why don't doing an example with newer versions, we're in 2024 man
Valid point 🙂 - will take care in the newest video
@truck.-kun.
If it doesn't matter and there is no difference so use the newest, today there is no difference but tomorrow you will have difference and compatibility problems, if you are in 2024 use the latest lte which is Java 21.
Why exactly are you adding the drivers when selenium 4.0 onwards it takes care of it automatically? Also, those xpaths are one of the most horrible things I’ve seen. You have absolute xpaths everywhere, change the code. It’s terrible.
Hi Ameya Godse: your point is valid - the xpaths used in this video are absolute xpaths and not relative xpaths. other point is related to chrome drivers - intention of this video was quick setup of framework and focus on couple of requests that came i.e: how to do reusability of methods in variety of testcases, extent reports, jenkins integration as mentioned in introduction. sure - will prepare on the focus area of xpaths and webdriver manager.
FreeMarker template error:
Template inclusion failed (for parameter value "partials/exceptıon.ftl"):
Template not found for name "spark/partials/exceptıon.ftl".
The name was interpreted by this TemplateLoader: ClassTemplateLoader(resourceLoaderClass=com.aventstack.extentreports.ExtentReports, basePackagePath="templates/" /* relatively to resourceLoaderClass pkg */).
Why does it give such an error, what is the solution?