plone / plone.app.robotframework

Provides Robot Framework compatible resources and tools for writing functional Selenium tests (including acceptance tests) for Plone CMS and its add-ons.
https://docs.plone.org/external/plone.app.robotframework/docs/source/index.html
11 stars 17 forks source link

Use plone.api for content keywords. #32

Closed tisto closed 6 years ago

tisto commented 10 years ago

@datakurre You removed plone.api as a dependency, right? Is the old code still available? What if we would submit a PLIP to allow plone.api in the core for testing purposes and then re-introduce plone.api? After that I would like us to think about ways to make the full plone.api available for robot keywords.

datakurre commented 10 years ago

@tisto I used plone.api only for creating content and users, yet both have evolved somewhat after dropping plone.api. So, a fresh start would be easier. If you have time, you can try it simply as a Python keyword library (remote libraries are not necessary with zope.testrunner).

You can already do Library plone.api.content in robot files, but of course, it may fail with no way to represent content objects in robot.

What I learned with the existing keywords, plone.api would require wrappers, which would translated paths and UIDs into objects and back between robot and plone.api. Not sure, though, would there be any generic ways to do that, or must we have wrapper keywords for every supported plone.api function.

https://github.com/plone/plone.app.robotframework/commit/d3abf5c87ffc1f83f9c023f31e27ab8ee5dfa9b1

jensens commented 6 years ago

Old, issue, I close this one, reopen if you think it worth to follow up here:

This would probably introduce a circular dependency, so -1 on this. First we need to get our dependency mess in Plone core cleaned up, and I dont see this happen soon.