StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4089199
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-11-03T16:22:41.123
FavoriteCount
0
LastActivityDate
2010-11-03T16:22:41.123
LastEditDate
LastEditorUserId
0
OwnerUserId
485654
ParentId
4087082
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
<code>cmd</code> is not <code>null</code>; however, <code>assertTrue</code> throws an <code>AssertionFailedError</code> with a <code>null</code> message. Either provide a default message (<code>assertTrue "default message", cmd.hasErrors()</code>) or just state, <code>assert cmd.hasErrors()</code>. So, let's see why <code>cmd.hasErrors()</code> returns <code>false</code>. - That's because the custom validator does not return <code>false</code>, but some string instead, that evaluates to <code>true</code> according to the "Groovy Truth". (There, the Grails API appears to have changed since the book has been published.) In the <code>LoginCommand</code> class, change <pre><code>login blank:false, validator:{ val, cmd -> if(!cmd.user) return "user.not.found" } </code></pre> to <pre><code>login blank:false, validator:{ val, cmd -> if(!cmd.user) return false } </code></pre> Then, the error code will be "LoginCommand.login.validator". If you need a custom error code, you can <a href="http://static.springsource.org/spring/docs/3.0.x/javadoc-api/org/springframework/validation/AbstractErrors.html" rel="nofollow">add an error object</a> yourself (without returning anything), like so: <pre><code>login blank:false, validator:{ val, cmd -> if(!cmd.user) cmd.errors.rejectValue('login', 'user.not.found') } </code></pre> P.S.: You <a href="http://markmail.org/message/o6iwawbq4ouxtztw" rel="nofollow">shouldn't use</a> the <code>MockUtils</code> class, directly, but instead <code>extend GrailsUnitTest</code>. Also, <code>MockUtils.prepareForConstraintsTests(Class)</code> is deprecated; moreover, it doesn't suit well for command objects. - Use the <code>mockForConstraintsTests(Class)</code> method instead, inherited from <code>GrailsUnitTest</code>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGrails 1.3.5 controller test nulls command object
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USrobbbert
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.