apache / apache/grails-intellij-plugin

Grails. Running functional test unexpected differences

Open
#268 0 comments 0 reactions 0 assignees View on GitHub
bug imported-from-youtrack
Dominant language
Java
Stars
17
Forks
4
Avg merge
5d 15h
Merged PRs (30d)
4

Description

I'm trying to run functional test with GEB and Remote Control plugin.
When I have an already running local-host app and I fire up functional testing the remote control seams not to be able to access the domains. (as it was not accessible Method on class [xxx] was used outside of a Grails application....)
But when I don't have a running app and the fired up functional test and the app is starting before the test execution the remote control has access to domains but the CSS are not leaded properly.

We are using java version 1.7.0_79, grails-2.4.3
build.config : compile ":remote-control:2.0"

The standard run off application is running Development environment and the run of functional testing is running environment test.

The issue with development is that Remote control is asking
```
String getFunctionalTestBaseUrl() {
System.getProperty(FUNCTIONAL_BASE_URL_PROPERTY)
}
```
And this returns [http://localhost:9001null/](http://localhost:9001null/) and in env test run it returns proper value.

---

*Imported from [IDEA-161615](https://youtrack.jetbrains.com/issue/IDEA-161615) · Type: Bug · Votes: 0*
*Comments, attachments, dates and reporter are not part of the export — follow the link above for the full history.*

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the functional test with Java 1.7.0_79, Grails 2.4.3, GEB, and Remote Control 2.0, comparing a running development app with an app started for the test environment. Inspect the functional test base URL, especially the reported http://localhost:9001null/ value, and the CSS loading behavior; done means domains are accessible and CSS loads in both relevant runs.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.