Skip to content

Extending DefaultMatcher from selenium Grid to accept some other custom values from your test

Notifications You must be signed in to change notification settings

TuHuynhVan/custom-matcher-selenium-grid-with-appium

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Introduction

  • To have flexibility on distinguish appium node via network based on Capabilities and unique device udid

Usage

  • mvn -q install -DskipTests and the jar file will be under target folder
  • OR you can use the jar file in 3.149.build
  • hubConfig.json example:
{
  "host": "192.168.1.202",
  "port": 4444,
  "newSessionWaitTimeout": 60,
  "servlets": [],
  "withoutServlets": [],
  "custom": {},
  "capabilityMatcher": "com.sdetpro.appium.grid.matcher.CustomCapabilityMatcher",
  "registry": "org.openqa.grid.internal.DefaultGridRegistry",
  "throwOnCapabilityNotPresent": true,
  "cleanUpCycle": 5000,
  "role": "hub",
  "debug": false,
  "browserTimeout": 0,
  "timeout": 90,
  "sessionTimeout": 90
}

  • Start Hub with command:

java -cp selenium-server-standalone-3.141.59.jar:selenium-grid-custom-matcher-3.141.59.jar org.openqa.grid.selenium.GridLauncherV3 -role hub -hubConfig hubConfig.json

CREDIT

selenium-grid-capability-matcher

About

Extending DefaultMatcher from selenium Grid to accept some other custom values from your test

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages