Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Change assertion subject when using ownProperty

See original GitHub issue

It would be nice if ownProperty changes the assertion subject in the same way as property does.

So you can do the following expectation:

expect(obj).to.have.ownProperty('foo')
  .that.is.a('string');

Issue Analytics

State:
Created 9 years ago
Comments:8 (6 by maintainers)

Top GitHub Comments

1reaction

sukrosonocommented, Mar 15, 2016

am i correct that this should be close since 641 have been merged?

1reaction

lucasfcostacommented, Mar 14, 2016

I’m planning on sending a PR for this today. If someone was already working on this please let me know 😃

Top Results From Across the Web

Configuring property assertions - IBM

In the Property field, specify the property to which you want this assertion to apply. You can either select a property from a...

Customize SAML Assertions - Auth0

Customize SAML assertions when Auth0 acts as the identity provider by configuring the addon in the Dashboard or by using rules.

Extensibility - Fluent Assertions

The Subject property is used to give the base-class extensions access to the current DirectoryInfo object. Execute.Assertion is the point of entrance into...

Chain .property() assertions on objects #193 - GitHub

Hello, is there a workaround to allow something like this: chai.expect({ foo: 'bar', bar: 'foo' }) .to.have.property('foo', ...

FluentAssertions Asserting multiple properties of a single object

You should be able to use general purpose Match assertion to verify multiple properties of the subject via a predicate response.Should() .