Download JAR files tagged by selenium with all dependencies

A test automation framework built on top of Cucumber. Intended to be used for writing various automated cucumber tests using external dependencies: - Cucumber: ${io-cucumber-ver} - Web UI Functional Tests: Selenium ${selenium-java-ver} - API Tests: RestAssured ${rest-assured-ver} Run tests using: - A Cucumber runner class for CICD setup - Built-in JavaFx Applet test runner to non-CICD setup using a fat jar c/o maven shade Report Results: - Credits to Damian Szczepanik and his project [cucumber-reporting] - Built-in reporting module [cissnei-report] forked and modified - https://github.com/damianszczepanik/cucumber-reporting

Allure Test Framework Selenium supports: * Malleable resolution * Remote Web Design * Mobile browsers * Support for many browsers * Internet Explorer, Edge * Chrome, Firefox * Safari * User friendly actions * elementCheckBox * elementDropdown, etc. * Ubiquise test execution * locally * against Selenium Grid through Jenkins * Page Object Model architecture * Selenium WebDriver with Java * Update Observers Based on Selenium 3.8.1

Test automation framework providing seamless integration of selenium based web GUI tests, file and stream content, and protocols. It enforces a unified programming model for testing different technologies: Web GUI including AJAX (using Selenium), HTML, XML, EDIFACT, Flat File, CSV/TSV, protocols like HTTP, JMS, FTP, SFTP, Network Shares. The framework is extensible via a flexible service API.

SeleniumJT is a Selenium2 wrapper framework that simplifies the coding required for getting you tests up and running fast. In addition to encapsulating the idiosyncrasies of Selenium WebDriver it also supplies a more reliable testing framework for dynamic web pages by allowing elements time for conditions to be met before failure, times that are fully customisable.

WebTest Fixtures are an extension to FIT/FitNesse that implement a customer-friendly language for web testing, utilising Selenium Remote Control. WebTest runs inside FitNesse, allowing you to integrate web UI tests into an automated build system, and use other FitNesse fixtures to talk to your domain model, prepare and verify database changes during Web UI tests. Both .NET and Java FitNesse runners are supported, and the library is released under GPL.

Test Drop-in Framework for Selenium WebDriver 4.1.x This repository contains these major deliverables: a) the Test Drop-in Framework, b) a WebDriver implementation offering enhanced logging capabilities, and c) the @FindByJS annotation support Provides a thin abstraction layer between the test environment and the test class plus its helpers. This makes the test code independent of the test environment, thus allowing exchange of tests between organizations or even companies. It comes with an event firing WebDriver wrapper plus corresponding interface. This allows you to implement listeners to arbitrary WebDriver activities for various purposes such as logging. Offers support of JavaScript commands to find elements in a way similar to @FindBy used on fields in Page Object classes.

Java, Selenium, Appium, Winium, Extend, and TestNG automated testing framework. Bichromate integrates the best of these frameworks and takes automation to the next level. With Bichromate there is one function call that builds any type of Web,IOS Mobile, Android, and Windows App driver on any platform (Windows, Mac, Linux). From Local web drivers, to SauceLabs, Browserstack, and Selenium grid. Build data driven tests is never easier. Bichromate also gives you built in Factories that, access DBs, Video Capture, FTP, POM Generation, Hilite element.

Geronimo integration testsuite. This contains 2 profiles, default and child. The default profile is used by the top level suites directly under this. The child profile is used by the test poms under the suites. This pom defines the basic dependencies needed by most suites. The start-selenium, start-server, invoke, and stop-server goals are globally configured here in the pluginManagement sections. They just need to be bound in the suites where needed and appropriate. The test poms under the suites should have this pom as their parent and set their relativePath appropriately The test poms under the suites inherit an empty 'child' profile from here. But any other build executions within the test poms should all be inside a 'child' profile.