jdi-testing / jdi-light Goto Github PK

Add few tests as example for using SauceLabs (remote driver)
* Implement SauceLabs properties file if necessary

Add ability to init all Page Objects in folder by command
And in default folder with no ations

Implement methods for Cucumber for html elements methods

See example in jdi-cucumber

1. Create new methods for Cucumber steps (Cucumber Core) - use request from the team
2. Implement steps for Cucumber
   2.1 Implement steps for Cucumber for Common Elements
   2.2 Implement steps for Cucumber for Complex Elements
   2.2 Implement steps for Cucumber for Composite Elements
3. Cover steps with tests - add JDI Light Cucumber dependency

Add tests for rest of html elements on html page and fix html elements if necessary

Add "unit-like" tests for each method of jdi-light elements marked with @JDIAction annotation
Table
FastTable
+ tests for complex cells
+ tests for tables as list of entities

Add examples how to switch Selenid project to jdi-light

Add Java docs for methods in jdi-light marked with @JDIAction annotation

Css and XPath > UI
New locators features
['text']
[*'text']
<
[3]

Tests with no locators and jdi markup for applications
See examples in tests https://github.com/jdi-testing/jdi-light/blob/master/jdi-light-examples/src/test/java/io/github/epam/tests/smart/path/PathTests.java

Add "unit-like" tests for each method of jdi-light elements marked with @JDIAction annotation
UIElement

While test fails we should do by default:

1. Put in log elements Html code
2. Highlight element on page
3. Make a screenshot

Test project structure
UI Page Objects
Test Data, Tests, TestInit
InitPageObjets (static, dynamic)

Buttons, Text Fields etc.

Add Java docs for methods in jdi-light-html interfaces marked with @JDIAction annotation

Add "unit-like" tests for each method of jdi-light elements marked with @JDIAction annotation

WebList
UIList with Section as Generic parameter
Dropdown

Use Smart search for mapping elements in form

test properties
WebSettings
DriverSettings
Run jdi tests via console (Jenkins as example)
properties from mvn params console
properties from gradle params console
Before all tests (example testng)
Kill run web drivers

We need to add description to all types of html elements
Html elements placed: http://epam.github.io/JDI/html5.html
Each section needs:

• TITLE
• Short description
• W3C link
• Mdn link
• Element Methods
• Link to code examples (later)

Html code can be changed in https://github.com/epam/JDI/tree/gh-pages

Add Java docs for all methods in jdi-light
Should be done after Add Java Docs for jdi-light core JDIAction

Add readme to project

Add examples how to switch Selenium project to jdi-light

Add Cook book for jdi-html

Implement Kendo UI Telerik typical elements support like html elements

Angular
React
Vue

Collections of elements
Collections of Sections

Implement Vue typical elements like html elements

Add list of test examples that should run in parallel (2-3 threads)

Generate Page Objects
Test attributes in code
Search elements rules

Add contribute rules in readme like Report portal did

Implement Bootstrap typical elements like html elements

Add Java docs for all methods in jdi-light-html
Should be done after Add Java Docs for jdi-light-html JDIAction

Examples with Table, Dropdown and Long Text
Stable search (no waits for page load and ajax-like elements, no thread sleeps)
Examples: Suspend and Ghost buttons.

Add ability to init static pages in some folder / folders directly without JDISite class
scan expected folder and init static PageObjects

How to run tests in parallel with examples
Local
Use Custom Driver

Integration with thirdparty tools:
Selenium Grid
Browser Stack
Selenoid

Tips on parallel tests limitations (preconditions, independent test data)

Dependency change
PageFactory Init
WebElement > UIElement
List<WebElement> > WebList or List<UIElement>

Immediate profits:
Logs
Stability
Performance
Code reduction with Forms and tables
Remove Thread sleeps and waits

Write documentation on all methods for
Section - This means to add different types of elements on section and validate that they are not null after Section init (via Site) and use Section (parent) locator as context

• public WebElement
• WebElement
• public static WebElement
• public TextField
• TextField
• public static TextField
• extend PageObject from some BaseClass that extends Section (public class Header extends BasePage; public class BasePage extends Section); place some elements on Base Page and validate that these elements are not null
• Create Section for IFrame with @frame annotation (use this page https://jdi-testing.github.io/jdi-light/index.html) and validate that elements in IFrame are intractable
• Validate that Base action also work for section (like isDisplayed and all is() validations)
• Add tests for PageObjects that not extend Section and placed on some WebPage

Form

• Validate all form actions
• Validate changing FILL_ACTION and GET_ACTION methods
• Validate filters functionality
• Add test for form with overridden fillAction() and getAction()

WebPage

• Add @url and @title validation tests with all combinations of these annotations params (including cases where some annotations missed)
• Add tests on all Page actions
• Add the same tests as for Section
• Add tests for PageObjects that not extend WebPage and placed on some Site

For examples for ChromeOptions add property file with options
And while Chrome driver init it will get properties from this file if any

Add ability to map custom attributes to way how to search element
Add default Annotations:
@ ById -> #elName
@ ByText -> //*[text()='elName']
@ ByClass -> .elName
@ ByType -> [type='elName']
@ ByName -> [name='elName']

Move all strings in exceptions and logs in jdi-light in settings class with public static String

Dependency change
PageFactory Init
SelenideElement > UIElement
ElementsCollection > WebList or List<UIElement>

Immediate profits:
Logs
Stability
Performance
Code reduction with Forms and tables
Remove Thread sleeps and waits

Add "unit-like" tests for each method of jdi-light elements marked with @JDIAction annotation
Forms
WebPages

Add few tests as example for using Selenoid (remote driver)
* Implement Selenoid properties file if necessary
Repository with project
https://github.com/jdi-templates/jdi-light-selenoid-template
Link to Selenoid Documentation: https://aerokube.com/selenoid/latest/

Standard forms features
Forms without locators
Inline Forms
Forms on pages (example Login Page/Form)

Tables
Fast Tables
Entity Tables

Setup tables
Asserts and search in Tables

Add first steps tutorial for beginners

Add test-examples for different kinds of site initialization using PageFactory.initElements

1. Init Site
2. Init list of WebPages
3. Init single WebPage
4. Init single page with no class in extends
5. Init list of pages with no class in extends
6. Init two different sites
7. Open two browsers in parallel
8. Work with 2+ sites in parallel tabs in one browser example

For now in jdi 1.0 all browsers are killed, even started not by Selenium. JDI Light doesn't handle this for now.