Coverage remained the same when pulling a7ed3d07cce34dcebf73ab425219826c4e7d077e on 1.7/199-setting-a-property-as-part-of-a-mock into 7fdf0886490d44de2c68a426fa8c212d01635d85 on release/1.7.
Coverage remained the same when pulling dd19d4062d71962c5016b53e0ccbb5d5fd52f227 on 1.7/199-setting-a-property-as-part-of-a-mock into 7fdf0886490d44de2c68a426fa8c212d01635d85 on release/1.7.
Coverage remained the same when pulling d3361a6c9570c14d844a9c6c5211ed4d7b906cf7 on 1.7/199-setting-a-property-as-part-of-a-mock into ab9e5dc4a316dcb43db749ce1885f31417e2ce0f on release/1.7.
Coverage remained the same when pulling 133c8980bf13ee2965696b12f7946eaeb7cef6f1 on 1.7/199-setting-a-property-as-part-of-a-mock into ab9e5dc4a316dcb43db749ce1885f31417e2ce0f on release/1.7.
Coverage remained the same when pulling 4452478ef52e519dafc65f60eff45217305486b6 on 1.7/199-setting-a-property-as-part-of-a-mock into ab9e5dc4a316dcb43db749ce1885f31417e2ce0f on release/1.7.
Coverage remained the same when pulling 16700d6ce5b1da2f8ae98ee42315d7f52c4f18de on 1.7/199-setting-a-property-as-part-of-a-mock into ab9e5dc4a316dcb43db749ce1885f31417e2ce0f on release/1.7.
You can set properties after the mock is created with
setProperty
but it would be nice to chain this functionality when creating the mock.