{"id":7609,"date":"2023-08-30T11:48:16","date_gmt":"2023-08-30T11:48:16","guid":{"rendered":"https:\/\/www.intexsoft.com\/?post_type=blog&p=7609"},"modified":"2023-08-30T11:57:33","modified_gmt":"2023-08-30T11:57:33","slug":"selenide-test-automation-using-selenoid-in-the-docker-container","status":"publish","type":"blog","link":"https:\/\/intexsoft.com\/blog\/selenide-test-automation-using-selenoid-in-the-docker-container\/","title":{"rendered":"Selenide Test Automation: Using Selenoid in the Docker Container"},"content":{"rendered":"
\n\t
\n\t\t\t\t\t
<\/div>\n\t\t\t\t
\n\t\t\t\n\t\t\t\t
\n\t\t\t\t\t\n\t\t\t\t<\/div>\n\t\t\t<\/a>\n\t\t\t
August 30, 2023 \u2022 by \t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\tDora &\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\tMargarita \n\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t\t

Selenide Test Automation: Using Selenoid in the Docker Container<\/h1>\n\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\tTech Staff\n\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t
\n\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\t\"image\"\n\t\t\t\t<\/picture>\n\t\t\t<\/div>\n\t\t\t<\/div>\n<\/section>\n\t\t\t\t\t\t\t\n\t\t\n\n\n
\n
\n\t\t
\n\n\n\n\t\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t

This article covers a basic Selenium project, including integrating TestNG and implementing a Page Object pattern. It also explores the features and benefits of Selenide, demonstrating its usage for elements, assertions, and waits. You will know how to incorporate the Selenoid framework to execute tests within or outside Docker containers.<\/p>\n

Reading time: 36 min.<\/p>\n\n\t\t\t\t\t<\/div>\n\t\t\t\t\n\t\t\t\t

\n\t\t\t\t<\/div>\n\t\t\t\t\t\t

 <\/p>\n

QA teams face an ongoing challenge to meet the increasing demands of software testing in today’s ever-evolving technological landscape. The need for efficient and reliable test automation solutions has become paramount. Enter Selenide Test Automation, a groundbreaking framework transforming QA professionals’ approach to testing.<\/span><\/p>\n

 <\/p>\n

At its core, Selenide Test Automation represents a significant shift in the software testing world. It offers an intuitive and streamlined approach to automate web application testing, enabling QA teams to achieve exceptional efficiency, accuracy, and speed in their testing processes. By harnessing the power of Selenide, QA professionals can elevate their testing efforts, ensuring the delivery of high-quality software products in record time.<\/span><\/p>\n

 <\/p>\n

Selenide Test Automation is a cutting-edge framework built on top of Selenium, a widely adopted automation tool for web browsers. It takes the Selenium experience to the next level by providing a simplified API, making it accessible for professional and personal usage. This means QA professionals no longer need to struggle with complex and lengthy code. Instead, they can write clean, concise, and highly readable test scripts that are easier to maintain and understand.<\/span><\/p>\n

 <\/p>\n

Equipped with a comprehensive set of features, Selenide Test Automation enhances the testing endeavors of QA professionals. Built-in assertions and smart waits eliminate the challenges of manual waiting and troubleshooting flaky tests. Selenide effortlessly handles dynamic elements, AJAX calls, and JavaScript-heavy applications, ensuring stable and robust test execution.<\/span><\/p>\n

 <\/p>\n

Furthermore, Selenide Test Automation seamlessly integrates with popular testing frameworks like TestNG and JUnit, enabling effective test management and reporting. The framework supports parallel test execution, empowering QA teams to leverage distributed environments or cloud-based platforms for faster and more efficient testing.<\/span><\/p>\n

 <\/p>\n

To maximize the potential of Selenide, we explore the integration of Selenoid in Docker containers. This powerful combination grants QA teams unmatched flexibility, scalability, and portability in their test environments. Testers can easily manage and orchestrate their testing infrastructure by leveraging Docker containers, ensuring reliable test execution within controlled and isolated environments.<\/span><\/p>\n

 <\/p>\n

In this article, we delve deep into the world of Selenide Test Automation, showcasing its transformative capabilities and the significant benefits it offers QA teams. We provide a comprehensive understanding of Selenide’s core concepts, simplified API, and unique features that position it as a game-changer in test automation. Additionally, we demonstrate the seamless integration of Selenoid in Docker containers, enabling the downloading binary and unlocking a new level of efficiency and scalability for your testing infrastructure.<\/span><\/p>\n

 <\/p>\n

Join us on this journey as we unveil the power and potential of Selenide Test Automation. Explore the remarkable benefits of this revolutionary framework and witness a significant improvement in test efficiency, accuracy, and overall software quality. With its intuitive and streamlined approach, Selenide Test Automation empowers QA teams to achieve outstanding results, confidently delivering high-quality software products. Embrace this robust implementation and revolutionize your QA efforts like never before.<\/span><\/p>\n

 <\/p>\n

 <\/p>\n\n\t\t<\/div>\n\t<\/section>\n\n\n\n

\n\t\t
\n\t\t\t
\n\t\t\t\t\t\t\t\t\t

Lack of DevOps specilists?<\/h3>\n\t\t\t\t\t\t\t\t\t\t\t\t\t
Deploy your product faster, decrease the time-to-market, and cut the overall project costs with IntexSoft<\/div>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\tSee more<\/a>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\n\t\t\t\t\t\t\t\t\"image\"\n\t\t\t<\/picture>\n\t\t<\/div>\n\t<\/section>\n\n\n
\n\t\t
\n\n\n\n\t\t\t\t\t\t\t\n\t\t\t\t
\n\t\t\t\t<\/div>\n\t\t\t\t\t\t

.<\/span><\/p>\n

.<\/span><\/p>\n

Selenium + TestNG. Selenium Maven<\/span><\/h3>\n

 <\/p>\n

We are considering a project build on the\u00a0<\/span>Maven<\/a>\u00a0builder, so we can find the project structure description in the\u00a0pom.xml<\/em>\u00a0file. To order use\u00a0Selenium+TestNG<\/b>, we should add appropriate dependencies to\u00a0pom.xml<\/em>\u00a0file. You can observe them between the\u00a0dependencies<\/i>\u00a0tags below:<\/span><\/p>\n

 <\/p>\n

                           <?xml version=\"1.0\" encoding=\"UTF-8\"?>\r\n                           <project xmlns=\"http:\/\/maven.apache.org\/POM\/4.0.0\"\r\n                                       xmlns:xsi=\"http:\/\/www.w3.org\/2001\/XMLSchema-instance\"\r\n                                       xsi:schemaLocation=\"http:\/\/maven.apache.org\/POM\/4.0.0 http:\/\/maven.apache.org\/xsd\/maven-4.0.0.xsd\">\r\n                              <modelVersion>4.0.0<\/modelVersion>\r\n\r\n                              <groupId>test<\/groupId>\r\n                              <artifactId>test<\/artifactId>\r\n                              <version>1.0-SNAPSHOT<\/version>\r\n                              <dependencies>\r\n                                       <dependency>\r\n                                                <groupId>org.seleniumhq.selenium<\/groupId>\r\n                                                <artifactId>selenium-java<\/artifactId>\r\n                                                <version>3.141.59<\/version>\r\n                                      <\/dependency>\r\n                                      <dependency>\r\n                                                <groupId>org.testng<\/groupId>\r\n                                                <artifactId>testng<\/artifactId>\r\n                                                <version>6.14.3<\/version>\r\n                                                <scope>test<\/scope>\r\n                                     <\/dependency>\r\n                            <\/dependencies>\r\n                          <\/project><\/span><\/pre>\n
 <\/p>\n
Here is the example of the Page Object:<\/span><\/p>\n
 <\/p>\n
import...\r\n\r\npublic class SignUpPage {\r\n   private WebDriver driver;\r\n\r\n   public SignUpPage(WebDriver driver) { this.driver = driver; }\r\n\r\n   private By emailField = cssSelector(\"#register-email\");\r\n   private By confirmEmailField = cssSelector(\"#register-confirm-email\");\r\n   private By passwordField = cssSelector(\"#register-password\");\r\n   private By displayNameField = cssSelector(\"#register-displayname\");\r\n   private By monthDropDown = cssSelector(\"#register-dob-month\");\r\n   private By dayField = cssSelector(\"#register-dob-day\");\r\n   private By yearField = cssSelector(\"#register-dob-year\");\r\n   private By shareCheckbox = cssSelector(\"#register-thirdparty\");\r\n   private By registerButton = cssSelector(\"#register-button-email-submit\");\r\n\r\n   public SignUpPage typeEmail(String email) {\r\n\r\n\tdriver.findElement(emailField).sendKeys(email);\r\n      return this;\r\n  }\r\n  \r\n  public SignUpPage typeConfirmEmailField(String email) {...}\r\n\r\n  public SignUpPage typePassword(String password) {...}\r\n\r\n  public SignUpPage typeName(String name) {...}\r\n\r\n  public SignUpPage setMonth(String month) {...}\r\n \r\n  public SignUpPage typeDay(String day) {...}\r\n\r\n  public SignUpPage typeYear(String year) {...}\r\n<\/span><\/pre>\n
 <\/p>\n
As we can see, there is a description of variables with locators for the elements of the registration page at the top of the java file. There are methods directly for interacting with elements of our page below the variable section.<\/span><\/p>\n
 <\/p>\n
Let\u2019s open the tests themselves:<\/span><\/p>\n
 <\/p>\n
private WebDriver driver;\r\n\r\nprivate SignUpPage page;\r\n\r\n@BeforeMethod\r\npublic void setUp() {\r\nSystem.setProperty(\"webdriver.gecko.driver\", \r\n\"C:\\\\Users\\\\Nikita\\\\IdeaProjects\\\\autotests_examples\\\\drivers\\\\geckodriver.exe\");\r\ndriver = new FirefoxDriver();\r\ndriver.manage().timeouts().impicitlyWait(10, TimeUnit.SECONDS);\r\ndriver.get(\"https:\/\/www.spotify.com\/us\/signup\/\");\r\n}\r\n<\/span><\/pre>\n
 <\/p>\n
As we can see, in the\u00a0@BeforeMethod<\/b>\u00a0annotation we describe what will have before each method.<\/span><\/p>\n
 <\/p>\n
@Test\r\npublic void typeInvalidYear() {\r\n     page = new SignUpPage(driver);\r\n     page.setMonth(\"December\");\r\n                 .typeDay(\"20\")\r\n                 .typeYear(\"85\")\r\n                 .setShare(true);\r\n      Assert.assertTrue(page.isErrorVisible(\"Please enter a valid year.\"));\r\n<\/span><\/pre>\n
 <\/p>\n
The\u00a0@Test<\/b>\u00a0annotation provides code for test methods.<\/span><\/p>\n
 <\/p>\n
   @AfterMethod\r\n    public void tearDown() {\r\n        driver.quit();\r\n    }\r\n<\/span><\/pre>\n
 <\/p>\n
The\u00a0@AfterMethod<\/b>\u00a0annotation contains the code that should be executed after each method.<\/span><\/p>\n
 <\/p>\n
When running tests using Selenium, the following will happen:<\/span><\/p>\n
 <\/p>\n