parsel vs. UI-licious vs. python-sql vs. zope.interface Comparison Chart

Stop writing brittle tests with hard-coded CSS, XPATH selectors and waits. Write tests that are meaningful to people, effortless to maintain, and reusable. The reason for this is because writing your tests using hard-coded CSS and XPATH selectors is like pouring concrete onto a specific UI implementation. This creates very high-maintenance tests that break at the slightest changes to the UI and are very hard for humans to read. UI-licious uses dynamic code analysis to understand the structure of your website based on the use of semantic HTML and ARIA accessibility attributes, as well as context of the previous commands, to identify which is the intended element to target for every command. This means that even if the HTML code for the UI changes underneath the code, the test is valid as long as the user journey remains the same. That said, your website doesn't to be written perfectly for UI-licious to work.

This package is intended to be independently reusable in any Python project. It is maintained by the Zope Toolkit project. This package provides an implementation of “object interfaces” for Python. Interfaces are a mechanism for labeling objects as conforming to a given API or contract. So, this package can be considered as an implementation of the Design By Contract methodology support in Python. Interfaces are objects that specify (document) the external behavior of objects that “provide” them. An interface specifies behavior through informal documentation in a doc string, attribute definitions, and invariants, which are conditions that must hold for objects that provide the interface. Attribute definitions specify specific attributes. They define the attribute name and provide documentation and constraints of attribute values. Attribute definitions can take a number of forms.