The Selenified Test Framework provides mechanisms for simply testing applications at multiple tiers while easily integrating into DevOps build environments. Selenified provides traceable reporting for both web and API testing, wraps and extends Selenium calls to more appropriately handle testing errors, and supports testing over multiple browsers locally, or in the cloud in parallel. It can be a great starting point for building or improving test automation in your organization.
Updates:
Bug Fixes:
Updates:
Bug Fixes:
NOTE: This release contains breaking changes. Following SemVer, the minor version was bumped, to indicate such. Updates:
testSite instances were replaced with appUrl for consistent naming. NOTE: this is a breaking change, and code using these methods will need to be updated.
Bug Fixes:
NOTE: This release contains breaking changes. Following SemVer, the minor version was bumped, to indicate such. Updates:
class level, instead of the previous entire Suite levelCHECK result. NOTE: this is a breaking change, and code written to directly call the detailed reporter will need to be updated.
acceptCertificate method was written to handle certificate incompatibility issues for IE and Edgelocation methods were renamed to url to match and provide common pattern for access the current browser URLfocus method was added to allow a test to focus on an element without clicking on it (similar to tabbing over to the element)editable method added. Essentially, Is the method an input and enabledget() table methods now return Elements instead of WebElements or a list of WebElements. As part of this, the numbering schema also changed, now referencing first column and row should be with 0. NOTE: this is a breaking change, and code using these methods will need to be updated.
verify, assert, waitFor. Verify performs a check, and on failure, logs the error and keeps moving forward with the test (what the old assert did). Assert performs a check, and on failure, immediately quits the test. WaitFor performs a check, and waits for the expected result. If it doesn't occur, logs the error and keeps moving forward with the test (what the old waitFor did). NOTE: this is a breaking change, and code using these methods will need to be updated.
waitFor methods were added, which align with the assert and verify methodsUpdates:
Updates:
Updates:
Updates:
Updates:
Updates: