You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we call getEmbeddedInstance on the object of the domain class, we must verify all fields. In the current test cases that I have written here, https://bitbucket.org/causecode/nucleus/pull-requests/40/add-embedded-user-class/diff#Lsrc/test/groovy/com/causecode/user/UserSpec.groovyT96
I am checking for some of the fields only in then block.If one or more fields which are not added in then block get deleted or not initialized properly in the domain class, this will have no effect in the unit test but the unit test should be failed.
This issue is created to add all such left embedded fields while checking in then block.
Originally reported by: Shivam Pandey (Bitbucket: shivamcausecode, GitHub: shivamcausecode)
When we call getEmbeddedInstance on the object of the domain class, we must verify all fields. In the current test cases that I have written here,
https://bitbucket.org/causecode/nucleus/pull-requests/40/add-embedded-user-class/diff#Lsrc/test/groovy/com/causecode/user/UserSpec.groovyT96
I am checking for some of the fields only in
then
block.If one or more fields which are not added inthen
block get deleted or not initialized properly in the domain class, this will have no effect in the unit test but the unit test should be failed.This issue is created to add all such left embedded fields while checking in
then
block.The text was updated successfully, but these errors were encountered: