StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhy doesn't HttpClient tear down properly between unit tests in grails
primarykey
Id
9894228
data
AcceptedAnswerId
10044708
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-03-27T17:02:28.220
FavoriteCount
0
LastActivityDate
2012-04-06T14:12:42.560
LastEditDate
2012-03-27T18:56:53.720
LastEditorUserId
253412
OwnerUserId
253412
ParentId
0
PostTypeId
1
Score
0
ViewCount
183
LastEditorDisplayName
text
Body
I have two Controller unit tests and each one sets an HttpClient metaclass execute in setUp() like the following: <pre><code>HttpClient.metaClass.execute = { HttpUriRequest request -> <return expected data for my tests> } </code></pre> Then I attempt to tear down the metaClass in tearDown() with the following code: <pre><code>protected void tearDown() { super.tearDown() GroovySystem.metaClassRegistry.removeMetaClass(HttpClient.class) } </code></pre> However only one of my unit tests passes because the return from the HttpClient is incorrect/unexpected. If I add the logic needed for both tests in the metaClass.execute of both tests I get no testing failures. However this is cumbersome and impractical, especially in an agile development environment. What am I doing wrong with trying to tear down this HttpClient metaclass registration? How can I troubleshoot this further? I'm currently using grails 1.3.7 on a CentOS 5 install. Edit: I should clarify that my problem is that the metaClass override is causing issues between test classes, not test cases. We've been setting up the metaClass override so that it will return correct data for all of the test cases in a given class. So Test class A has the metaClass data for it's test cases and Test class B has the metaClass data for it's test cases. The issue is that since Test class A gets tested first, test class B ends up using the metaClass definition from test class A and fails because of this.
Tags
<testing><grails><httpclient>
Title
Why doesn't HttpClient tear down properly between unit tests in grails
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. UStwilbrand
UserOwnerUserId
1. UStwilbrand
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
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.