Often we see dependency in test cases. one test case is dependent on output or end state of the other test case. TestNG provides an option to perform it.
Long time back i have posted article on accelerating the test execution using headless mode, Headless Browser For Accelerating Your Test Automation. Google Chrome versions before 59, headless execution had to be done by third-party headless browsers like PhantomJS, SlimerJS, TrifleJS, Nightmare, CasperJS and HTMLUnit.
It means, browsers uses third party engines to execute tests on headless mode and not native engine of the browser below are list of headless browsers and engines used by them to execute the test in headless mode.
TestNG is a testing framework developed in the lines of JUnit and NUnit. It is mainly use to execute the Unit test cases and now a days automated test cases. It has more advance features than Junit and NUnit.
Capturing the screenshots during test executing plays important role to analyzing the failures in test execution. these days, most of framework has image capturing features. this image capturing also acts as test execution proof of particular test. Selenium Webdriver provides …
When there are lot of automated test cases. automation team start facing problem with how to run them efficiently and get the result in lesser time. to resolve such issue, Selenium provides Selenium Grid. Selenium Grid allows you run your automation scripts or tests on different machines with different browsers in parallel.
In this lesson we will look at how we will selenium webdriver perform operations on different webelements such as links, buttons, textbox, dropdowns etc. often we do not get consolidated list of operations over webelements, This post will help you in it.
While automating the application most important part is identified objects. while identifying the objects we have make sure that object which we have identified is “Consistently Identified”. In Lesson no 8 we have seen several ways by which we can identify the elements. this lesson will focus on how we will identify the elements using Firebug.
There are several ways to identity the web elements. selenium webdriver provides different methods to identify these elements. most popular way is xpath. we can define or construct the xpath in different ways and for automation tester it is always a challenge to select or construct proper xpath so that it will not broke easily by some changes in the UI. but it has one disadvantage that it makes your execution slow. In this post we will see all method and different ways to identify the web elements.
In this Lesson we will create selenium script from scratch in eclipse. many times it found that automation engineer struggles with writing script from scratch. it is mainly happen because either you are new to selenium or you are using existing automation framework in which initiation and closure part of script is already defined.