Automation Trivia

                 Most of the people end up saying of integrating the Selenium Test suite with any one of the Continuous Integration server (Jenkins, Bamboo,..etc) to trigger the execution after build deployment. The suite may be Sanity, Smoke or Regression Test suite. But here challenging part is the CI tools mostly run on Linux box and we may not have expected browser installed in it. I have listed some solutions for CI, 1) Change the Selenium test suite browser configuration and execute it using HtmlUnitdriver or PhantomJSDriver ( Headless execution)        The importance of having “headless” tests is:     a) The majority of Linux server and Windows Core Servers deployments doesn’t have GUI at all     b) To avoid opening the browser in the foreground during the build agent is being used for desktop applications testing which require focus  Execute the Automation Test suite using HtmlUnitdriver by making a simple change in the test    script browser configuration and com

We always wonder that we have Test scripts to send an Email report to all the stakeholder with extensive report with count of Passed and failed after test suite execution but no logical test script to log the defect for the failed test cases in the Test management Tool. It might not affect much if we are working in conventional methodology like waterfall, protype etc. But we are in the level of deploying the products by adhering to the Continuous Delivery and Continuous Deployment process. So, to cope up the automation activities with the product deployment, the Product management tool – Jira provides an additional feature of updating/defect logging using test scripts by providing REST Api. Now we will look the implementation of Defect logging script, Pre-requisites :  Need below mentioned two Jars files in the build class path. Apache HttpClient 4.5.3 API - https://mvnrepository.com/artifact/org.apache.httpcomponents/httpclient/4.5.3 jersey-client.jar - http:/