Closed rodfersou closed 5 years ago
@hvelarde FYI
@rodfersou Thank you for your PR. Could you please add a test which assures the changed behaviour?
@hvelarde done @icemac can you please point me an widget test example?
There is no test for this widget in this package.
@rodfersou The OrderedSelectWidget
is tested in this doctest: z3c/form/browser/orderedselect.rst. Maybe you could use some of the code in this file to create a new unittest as the doctest also serves as documentation and should not contain too many edge case tests.
@icemac I am having some trouble to finish this PR https://github.com/zopefoundation/z3c.form/issues/78
@icemac I think this change in test is sufficient, please take a look
looks like I break something.. that's weird..
@icemac did you see my changes?
@rodfersou Did you already sign the Zope Committer Agreement? It will allow you to merge the PR on your own. (That's the policy in the zopefoundation
repositories.)
@icemac no, I didn't.. just the Plone Agreement
@icemac signed and sent the email :-)
@icemac a release would be appreciated
@rodfersou Currently the tests are failing on master
, see https://travis-ci.org/zopefoundation/z3c.form/jobs/436732823. Are you willing to look into these failures. I think they have to do with new releases of e. g. zope.schema
.
@icemac wow! last month they did 6 releases at zope.schema
!
can someone guide me on what is going on?
I looked over the test output. Everything looks cosmetic, and all related to raising more specific exceptions with different error messages than before (from both zope.schema and zope.configuration). That's great for code when you can except SomethingSpecific as ex
and access attributes of ex
that provide you with actionable information, but it does expose the fragility of doctests like this.
I did some work on fixing the tests for the 3.x branch which can probably be easily merged to master: https://github.com/zopefoundation/z3c.form/commit/4421dc42d1f453f0dc6c976dc0aba4dfba69fc79
great!
fix #75