Skip to content

Releases: siostechcorp/coseng

COSENG v2.2.0

02 Dec 19:59
Compare
Choose a tag to compare
  • Added newWebElements to CosengRunner
  • Adjusted WebElements to instaniate with a By so that a subsequent findAll() will use the webDriver.findElements() and populate the object with the list of found web elements
  • Ability to objectify a Selenium web element as a COSENG web element

COSENG v2.1.0

11 Nov 21:39
Compare
Choose a tag to compare

Building on v2.0.0

  • Added configurable maxExecutionTimeMinutes. Had fixed test execution limit of 5 minutes.
  • Added configurable setting for browser dimensions or maximize during web driver start
  • Added finding of href/src urls on a page, checking accessible and saving a report on found links and status (accepts invalid certs)
  • Added elapsed time counters for individual and total test times
  • Removed thread sleep for pause and just made a cpu burner instead of confusing thread management
  • Refactor demo tests to be a bit more distinct in execution; included an example of the find and save url features (actual checks for accessible are commented out for demoer to enable)
  • Refactor screenshot save paths
  • Refactor temp paths for test xml to allow better flexibility in test naming
  • Refactor TestNG report path naming for clearer delineation of test runs
  • Handle web driver management for suites of suite-files (of suite-files (of suite-files (of suite-files)))
  • Add explicit and configurable denotation of Angular2 apps
  • Deprecated WebDriverUtil and WebDriverToolbox. Unnecessary extra call to access convenience methods that could be served directly from CosengRunner

COSENG v2.0.0

18 Oct 20:11
Compare
Choose a tag to compare

COSENG v2.0.0 final; supporting Selenium 3.0.1 and TestNG 6.9.13.6. Supporting platform: Linux, Win10. Supporting browser: Google Chrome, Mozilla Firefox on both platforms and Microsoft Edge and Internet Explorer 11. Faithfully conducts concurrent Selenium web driver tests for TestNG suite parallel="none|tests|classes|methods" as well as introducing the oneWebDriver feature. Enabling oneWebDriver starts a single web driver instance that is used across multiple suites. Having one web driver allows for the suite test classes to use the same web driver instance for all testing.