jfinkhaeuser/unobtainium

Obtain the unobtainable: test code covering multiple platforms

unobtainium's Issues

PathedHash may need more methods such as :merge!

FIXME found

https://codeclimate.com/github/jfinkhaeuser/unobtainium/lib/unobtainium/pathed_hash.rb#issue_570e331ee305ab0001265a6e

Increase test coverage

ssia

Test ticket from Code Climate

Reset driver after scenario

After do |scenario|
  begin
    driver.reset
  rescue => error
    # if driver reset isn't possible, it doesn't make sense to continue
    puts "DRIVER RESET WASN'T POSSIBLE DUE TO #{error} - BUT IS REQUIRED "\
      "FOR BEFORE NEXT SCENARIO. WILL EXIT THE PROGRAM"
    driver.quit
    Kernel.exit(2)
  end

For the selenium driver, add client extensions

• Applies to selenium driver and possibly appium driver (research)
• Make it driven by some option

Expose wait method from Selenium

Currently only driver and config are exposed.
It would be good to be able to use the wait without having to require selenium.

Deprecate own PathedHash implementation in favour of collapsium

See collapsium

This might also help with #8, as PathedHash is not 100% covered.

Add a phantomjs driver

• It should re-use the selenium driver.
• It should use https://rubygems.org/gems/phantomjs to download and run phantomjs.
• It should then run the selenium remote driver against phantomjs.
• It should (at least) honour phantomjs' --webdriver-* options.

Only warn about server URLs if they differ

In appium_lib.server_url and options['url']

Take screenshots on failures

After do |scenario|
  if scenario.failed?
   # Time.zone = 'Berlin'
    timestamp = Time.zone.now.to_s.split(" ")[0, 2].join("_")
    filename = "failure-" + scenario.name.tr(" ", "_") + "-" + timestamp + ".png"
    take_screenshot(filename)
  end
end

Extend config syntax with an include mechanism

For projects configuring many different drivers, it may make sense to split the configuration conceptually into two parts: one that provides driver configurations, and one that provides other configuration values (which may include the driver to use by default).

Neither YAML nor JSON support including files. The config parser could be extended to interpret an 'include' key, e.g.

---
include:
 - some_file.yml
 - some_other_file.json

vs.

{
  "include": ["some_file.yml", "some_other_file.json"]
}

(Yes, we could mix configuration file languages)