Fork me on GitHub
#test-check
<
2019-05-09
>
ben09:05:20

Right, so that’s some of them. I also have a couple with • read from the db (inserted in test migration) • call a fn to modify the data • read from the db again • check that it has been modified as expected Do you think this should follow the same pattern, @gfredericks? Thanks

gfredericks10:05:17

@ben606 that's what I would do, yeah; do you reset the db from within the defspec also? I think you'd want to

ben10:05:31

Yeah, it all takes place within a transaction, so none of the changes get persisted

gfredericks10:05:59

that sounds good; the main thing dictating granularity is what things are dependent on what generated data

ben11:05:06

makes sense. Thank you