tikhomirovsergey / primitive

primitive

Hi, guys! Here is one more lib that uses Selenium Webdriver.

I have no idea how to call it by now. So I named it as “Primitive”. I will change its name if I have any idea. :)

The general idea was to provide ability for automated test execution which would interact with browser window, web page, or web page elements. Also it should work with more than one instance of webdriver in multithread environment. I’m sure it would be useful for developing automated test cases of any complexity.

Now it is rather rough and has some issues but still works. Also, I am sorry for my English in comments to source code. My excuse is that I had not enough time for good translation from Russian. But all these problems will be fixed while I am working on projects with the following tools: Html Elements (by Yandex) and thucydides.

You can check out sources.

I made it just for fun.

primitive's Issues

I think that constructors of any webdriver encapsulation are excessive. If it is this constructors will be reduced

Wiki page and documentation are need to be made.

https://github.com/TikhomirovSergey/primitive/blob/master/primitive/src/main/java/org/primitive/webdriverencapsulations/localserver/LocalRemoteServerInstance.java has to be removed. It need to be used only by tests

Refactor of UnhandledWindowChecker class.

1. Listener of UnhandledWindowChecker object should be made up.
2. There should be a common implementation of the new interface. It should work with Log and Photographer.
3. I think it makes sense to remove deprecated methods

Original webdriver should be sealed inside https://github.com/TikhomirovSergey/primitive/blob/master/primitive/src/main/java/org/primitive/webdriverencapsulations/firing/ExtendedEventFiringWebDriver.java.

I am working on integration with external API. ExtendedEventFiringWebDriver wraps an original instance of webdriver and implements WrapsDriver. This API could unpack this one.

Taking screenshots and highlighting elements should be divided between different classes

Taking screenshots and highlighting elements should be divided between different classes

It needs to add IPhoneDriver support.

It needs to add IPhoneDriver support.

Webdriver services are have to be used to provide local work with Chrome, Internet Explorer and PhantomJS.

Classes that are nested in Configuration.java should be implemented as classes by themself.

Screenshots should be named like this pattern: "picture_" + hashcode + ".png"

Classes ChromeDriverExe, IEDriverExe and PhantomJSDriver have to be renamed.

*.exe is for Win.
... but *.dmg is for Mac.

I think that *DriverExe misleads user.

Listener of browser window events

There should be a listener of browser window events.
Its basic implementation will work with Log and Photographer.

ClosedFiringWebDriver should be divided and removed.

https://github.com/TikhomirovSergey/primitive/blob/master/primitive/src/main/java/org/primitive/webdriverencapsulations/ClosedFiringWebDriver.java

It is a God Object, that obstruct changes . Also, all nested classes duplicate these classes (https://github.com/TikhomirovSergey/primitive/tree/master/primitive/src/main/java/org/primitive/webdriverencapsulations/webdrivercomponents).

I did this a year ago because I had not much knowlege about WebDriver and its components and I faced up a problem with multithread working against Internet Explorer.

Now I know how it should work without excessive classes.

Run tests on Mac.

It needs to think about ios-driver usage. Mobile application testing.

It needs to add PhantomJSDriver support.

It needs to add PhantomJSDriver support.

I can't add maven dependency on PhantomJSDriver. See here: Release needed against Selenium 2.35 API changes https://github.com/detro/ghostdriver/issues/260

It needs to wait for fix of this issue.

It needs to think about Selendroid usage. Mobile application testing.

https://github.com/TikhomirovSergey/primitive/tree/master/primitive/src/main/java/org/primitive/poweredbytestng should be isolated. It should be the project by itself.

To remake this using Java 8.

It needs to think about Appium usage. Mobile application testing.

It needs to add AndroidDriver support.

It needs to add AndroidDriver support.

Configuration. I think it is more comfortable to use JSON files instead of XML.

All classes are nested in WebDriverEncapsulation should be present by themself.

All classes are nested in WebDriverEncapsulation should be present by themself

Element highlighting doesn't work on mobile application. Android.

I tried to make test script like this:
https://github.com/appium/appium/blob/master/sample-code/examples/java/testng/src/test/java/com/saucelabs/appium/AndroidContactsTest.java.

Unfortunately, I faced up this:

org.openqa.selenium.NoSuchElementException: An element could not be located on the page using the given search parameters. (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 23 milliseconds
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '2.39.0', revision: '14fa800511cc5d66d426e08b0b2ab926c7ed7398', time: '2013-12-16 13:18:38'
System info: host: 'hp', ip: '192.168.0.104', os.name: 'Windows 8', os.arch: 'amd64', os.version: '6.2', java.version: '1.7.0_51'
Session ID: ff982ff9-4571-4493-b389-bf0bf7fa1c65
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Capabilities [{app=c:\Eclipse\ContactManager.apk, platform=WINDOWS, javascriptEnabled=true, databaseEnabled=false, browserName=, app-package=com.example.android.contactmanager, webStorageEnabled=false, device=Android, app-activity=.ContactManager, takesScreenshot=true, version=4.2}]

It happens when webelement is highlighted by its CSS change.