DDevelopment & Design

Już za miesiąc GeeCON w KrakowieGeeCON in Kraków, only one month left

Rejestracja trwa. W tym roku ta – jedna z najważniejszych w Polsce – konferencja javowa świętuje swoje piąte urodziny. Część naszego zespołu wybiera się do Krakowa w dniach 15-17 maja. A Wy?Registration is going on. One of the most important in Poland Java conference celebrates 5th birthday this year. A part of TouK team will be there 15-17 May, will you?

Rejestracja trwa. W tym roku ta – jedna z najważniejszych w Polsce – konferencja javowa świętuje swoje piąte urodziny. Część naszego zespołu wybiera się do Krakowa 15-17 maja. A Wy? GeeCON 2013

Registration is going on. One of the most important in Poland Java conference celebrates 5th birthday this year. A part of TouK team will be there 15-17 May, will you?


GeeCON 2013

— Previous article

WJUG o testach

Next article —

Warszawa JUG z nową stroną

You May Also Like
DDevelopment & Design

Grails with Spock unit test + IntelliJ IDEA = No thread-bound request found

During my work with Grails project using Spock test in IntelliJ IDEA I've encountered this error:

java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.
 at org.springframework.web.context.request.RequestContextHolder.currentRequestAttributes(RequestContextHolder.java:131)
 at org.codehaus.groovy.grails.plugins.web.api.CommonWebApi.currentRequestAttributes(CommonWebApi.java:205)
 at org.codehaus.groovy.grails.plugins.web.api.CommonWebApi.getParams(CommonWebApi.java:65)
... // and few more lines of stacktrace ;)

It occurred when I tried to debug one of test from IDEA level. What is interesting, this error does not happen when I'm running all test using grails test-app for instance.

So what was the issue? With little of reading and tip from Tomek Kalkosiński (http://refaktor.blogspot.com/) it turned out that our test was missing @TestFor annotation and adding it solved all problems.

This annotation, according to Grails docs (link), indicates Spock what class is being tested and implicitly creates field with given type in test class. It is somehow strange as problematic test had explicitly and "manually" created field with proper controller type. Maybe there is a problem with mocking servlet requests?