Closed jacobian closed 5 years ago
@jacobian could add some tests for Bluprint.make
and Blueprint.make_one
as well?
@fcurella BlueprintTest.test_blueprint
calls Blueprint.make
; is that good enough for the make
case or would you prefer a specific test for that method? And for both, should I include something with .fields().make()
/ .fields().make_one()
as well? I'm not sure how granular you want tests here but I don't feel strongly myself, so lmk and I'll do the needful.
@jacobian Coveralls shows these 2 lines as missing coverage:
https://coveralls.io/builds/26358141/source?filename=django_fakery/blueprint.py#L40 https://coveralls.io/builds/26358141/source?filename=django_fakery/blueprint.py#L69
TBH all I care is that those if
branches are hit at least once during the full test run
@fcurella 👌 ah perfect, I'll do that. Thanks!
Well... I fixed the coverage thing, but now a seemingly-unrelated test is failing. It passes locally, so I'm not sure what's up.
@jacobian I've re-run the job and test is passing. I'll have to look into it later.
Thank you so much for your PR!
This will fix #50.
This makes
Blueprint.fields()
return a new Blueprint, with updated fields, instead of overwriting the fields on the blueprint.