|
On 7/16/19 8:12 PM, Anuj Borah wrote:
@Mark Reynolds
@Mark Reynolds
>>> The code itself looks fine to me, but I find it
odd you are testing matching rules by creating COS entries
in two of those PRs.
Cos entries are used here as part of (
objectclass: extensibleObject
)
As cos template has (
objectclass: ['top','cosTemplate' , 'extensibleObject']
)
Which is the nearest one of row extensibleObject entry.
Ah okay I see. Please add a comment that you are really just
trying to use an entry with extensibleObject, because it is
currently confusing.
Thanks for providing more background on this. The rest looks
good to me.
Thanks,
Mark
@Mark Reynolds
>>> The code itself looks fine to me, but I
find it odd you are testing matching rules by creating COS
entries in two of those PRs.
Cos entries are used here as part of (
objectclass: extensibleObject
)
As cos template has (
objectclass: ['top','cosTemplate' , 'extensibleObject']
)
Which is the nearest one of row extensibleObject
entry.
>>> I don't think that is actually doing
anything in regards to matching rules. I was under the
impression that matching rules are only applied/enforced
during searches (not Adds or Modifies). So you are
checking for TYPE_OR_VALUE_EXISTS errors in some of the
tests, and I don't see what that has to do with matching
rules. Or, maybe I am just missing what this test is
trying to do as I am not that familiar with MRs. So if
you can clarify that for me I would appreciate it
Please refer bellow ldif file and TET Filter suit which
is part of Filter test suit . To See whats going
on Please see the original TET Filter suit . ( test
series mr_*() )
Regards
Anuj Borah
--
389 Directory Server Development Team
|
