You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Temporarily revert the part of my earlier pull request Do not use run_on_failure from Selenium2Library. #57 that removes the run_on_failure: it works wonders on Plone coredev, but may be too invasive in a bugfix release. We do keep the new Plone Test Setup and Plone Test Teardown keywords.
Release this as 0.9.17 and create maintenance branch 0.9.x.
Revert the temporary revert of run_on_failure on master branch.
Release 1.0. Use that in coredev 4.3 and higher.
The text was updated successfully, but these errors were encountered:
Shipping without using this feature is too big a change for a patch release.
I will release 0.9.17 without this, make a 0.9.x maintenance branch,
and then on master revert this change and release 1.0.
See #61
I can make a release, but fine if someone else does it.
I propose the following:
Fail Unless Equal
withShould Be Equal
in test. #59 and Test with robotframework 3 #60). [edit: done myself]run_on_failure
: it works wonders on Plone coredev, but may be too invasive in a bugfix release. We do keep the newPlone Test Setup
andPlone Test Teardown
keywords.run_on_failure
on master branch.The text was updated successfully, but these errors were encountered: