Package Exports
- jasmine-proptype-matcher
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (jasmine-proptype-matcher) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Jasmine PropTypes Matcher

Use the type checking power of React prop-types
as a matcher in Jasmine.
Frameworks like Enzyme or Jest are great for checking our component props against defined PropTypes. However there is more to your application to just components. Jasmine proptype matcher steps in to assert the other objects and values of your code using your already defined propTypes.
When writing unit tests for your redux actions and reducers use your Component.propTypes
to make sure your are correctly formating the store's data being sent to your components. Even if you are not using React you can still use PropTypes and Jasmine proptype matcher to create a robust type checking unit tests for any project.
Install
npm i -D jasmine-proptype-matcher
Usage
import PropTypes from 'prop-types';
import PropTypesMatcher from 'jasmine-proptype-matcher';
describe('testing with jasmine-proptype-matcher', () => {
beforeEach(() => jasmine.addMatchers(PropTypesMatcher));
it('asserts customShape', () => {
const customShape = PropTypes.shape({
id: PropTypes.string.isRequired,
count: PropTypes.number,
});
expect({ id: '0987', count: 123 }).toBePropType(customShape);
expect({ count: 123 }).not.toBePropType(customShape);
expect({ id: '0987', count: [] }).not.toBePropType(customShape);
});
});
API
Jasmine PropTypes matcher provides two new matchers to Jasmine's expect:
toBePropType
Checks a single value against and single propType. If prop-type validation fails the expect will fail and report the error from prop-types.
expect('hello world').toBePropType(PropTypes.string);
expect('hello world').toBePropType(PropTypes.number);
// Throws: Invalid hello world `value` of type `string` supplied to `toBePropType`, expected `number`.
toBeValidPropTypes
Checks an object of values against and object of propTypes. If an propType is missing for a key in values, the key is not validated. This follows the smae behavior as PropTypes.checkPropTypes
expect({
id: '123',
count: 10,
children: ['456'],
}).toBeValidPropTypes({
id: PropTypes.string.isRequired,
count: PropTypes.number,
children: PropTypes.arrayOf(PropTypes.string)
});
Compatibility
PropTypes v15.6
Jasmine proptype matcher has a peer dependency to prop-types
15.6 or greater. Make sure your project has prop-types installed as a dependency.
Jasmine v2.8
Jasmine proptype matcher is tested using jasmine v2.8. Lower versions are untested, results may vary.
npm i --save prop-types jasmine