Github user benkeen commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/546#issuecomment-145589313
Boy, this proved to be an absolute devil to test. I tried different methods
of altering the DOM to set the form field values without triggering a change,
but nothing worked. That actually makes a whole lot of sense since the whole
*point* of React is that there's a 1-1 map between the fields + state in cases
like this.
The best I could come up with was adding a couple of component props
intended to test this precise condition. The test uses them to confirm that
non-state values are passed to the login action. I don't much like it, but it
confirms the component works as expected for this given clause. Better ideas
welcome!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
