projects / civicrm-core.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 5231025) | patch
CRM-19074 attempt to replicate the bug in a test
authoreileen <emcnaughton@wikimedia.org>
Thu, 21 Jul 2016 04:02:20 +0000 (16:02 +1200)
committereileen <emcnaughton@wikimedia.org>
Wed, 27 Jul 2016 21:49:58 +0000 (09:49 +1200)
commit4ac6bdf3ddb3a17e0eb8448cbc81e704bb2ce7a4
tree179073e5bcfd8e64ba72b17414ec57076ea564fatree | snapshot (zip tar.gz)
parent52310253dc0940542dfd386ca6afbafcdaf9d1a1commit | diff
CRM-19074 attempt to replicate the bug in a test

I didn't actually succeed in replicating it - although I increased coverage.

The issue is that when there is no consistent differentiation
between a custom checkbox field which is no set vs one that
has been set to empty(unchecked).

There is an inconsistent data storage difference whereby it is sometimes stored as an empty string & sometimes as NULL but this does not seem to be something
that is deliberate.
tests/phpunit/api/v3/JobTestCustomDataTest.php diff | blob | blame | history