【问题标题】:"grails test-app * " never enters breakpoints“grails test-app *” 从不进入断点
【发布时间】:2015-04-15 13:03:18
【问题描述】:

我使用命令 "grails test-app *" 运行集成测试。 测试成功运行,但从未达到我的断点。 我使用intellij grails配置,按shift+F9调试,但调试没有任何效果。

BuildConfig.groovy

grails.servlet.version = "3.0" // Change depending on target container compliance (2.5 or 3.0)
grails.project.class.dir = "target/classes"
grails.project.test.class.dir = "target/test-classes"
grails.project.test.reports.dir = "target/test-reports"
grails.project.work.dir = "target/work"
grails.project.target.level = 1.6
grails.project.source.level = 1.6
//grails.project.war.file = "target/${appName}-${appVersion}.war"

grails.project.fork = [
    // configure settings for compilation JVM, note that if you alter the Groovy version forked compilation is required
    //  compile: [maxMemory: 256, minMemory: 64, debug: false, maxPerm: 256, daemon:true],

    // configure settings for the test-app JVM, uses the daemon by default
    test: [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256, daemon:true],
    // configure settings for the run-app JVM
    run: [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256, forkReserve:false],
    // configure settings for the run-war JVM
    war: [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256, forkReserve:false],
    // configure settings for the Console UI JVM
    console: [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256]
]

grails.project.dependency.resolver = "maven" // or ivy
grails.project.dependency.resolution = {
    // inherit Grails' default dependencies
    inherits("global") {
        // specify dependency exclusions here; for example, uncomment this to disable ehcache:
        // excludes 'ehcache'
    }
    log "error" // log level of Ivy resolver, either 'error', 'warn', 'info', 'debug' or 'verbose'
    checksums true // Whether to verify checksums on resolve
    legacyResolve false // whether to do a secondary resolve on plugin installation, not advised and here for backwards compatibility

    repositories {
        inherits true // Whether to inherit repository definitions from plugins

        grailsPlugins()
        grailsHome()
        mavenLocal()
        grailsCentral()
        mavenCentral()
        // uncomment these (or add new ones) to enable remote dependency resolution from public Maven repositories
        //mavenRepo "http://repository.codehaus.org"
        //mavenRepo "http://download.java.net/maven/2/"
        //mavenRepo "http://repository.jboss.com/maven2/"
    }

    dependencies {
        // specify dependencies here under either 'build', 'compile', 'runtime', 'test' or 'provided' scopes e.g.
         runtime 'mysql:mysql-connector-java:5.1.29'
        // runtime 'org.postgresql:postgresql:9.3-1101-jdbc41'
        test "org.grails:grails-datastore-test-support:1.0.2-grails-2.4"
    }

    plugins {
        // plugins for the build system only
        build ":tomcat:7.0.55"

        // plugins for the compile step
        compile ":scaffolding:2.1.2"
        compile ':cache:1.1.8'
        compile ":asset-pipeline:1.9.9"

        // plugins needed at runtime but not for compilation
        runtime ":hibernate4:4.3.6.1" // or ":hibernate:3.6.10.18"
        runtime ":database-migration:1.4.0"
        runtime ":jquery:1.11.1"

        // Uncomment these to enable additional asset-pipeline capabilities
        //compile ":sass-asset-pipeline:1.9.0"
        //compile ":less-asset-pipeline:1.10.0"
        //compile ":coffee-asset-pipeline:1.8.0"
        //compile ":handlebars-asset-pipeline:1.3.0.3"
    }
}

【问题讨论】:

  • 您是从 grails 控制台还是 intellij 运行测试?
  • 我都用过,同样的输出...

标签: grails intellij-idea spock


【解决方案1】:

如果您从 grails 控制台运行测试,请在启动 grails 控制台时传递 --debug-fork 选项。例如grails --debug-fork,然后使用test-app 命令运行测试

或者只是在你的 BuildConfig 中的这一行 test: [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256, daemon:true] 中将调试标志更改为 true

您必须在 intellij 中创建远程调试配置才能连接到端口 5005。(运行 > 编辑配置 > 添加新配置 > 远程,并将端口更改为 5005)

当 grails 控制台上显示“Listening for transport dt_socket at address: 5005”时,使用 Run > Debug 从 intellij 附加调试器并选择之前创建的远程调试配置。

【讨论】:

  • 或作为替代禁用分叉
  • 所以我必须运行我的应用程序才能进行集成测试?
  • 不,你只需要测试应用程序
  • 我创建了新的 grails 配置 -> "test-app --debug-fork YourClassNameIntegrationSpec --verbose --echoOut" 。之后,我使用端口 5005 上的远程配置创建并连接。在集成测试中调试 WORKS!
【解决方案2】:

我只是在 BuildConfig 中执行此操作,一切正常:

grails.project.fork = [
    test: false
]

它可以在第一个 grails.project.fork 配置之后进行覆盖。

【讨论】:

    【解决方案3】:

    你必须在你的 BuildConfig.groovy 中注释这一行

    test: [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256, daemon:true],
    

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 1970-01-01
      • 2012-09-17
      • 1970-01-01
      • 1970-01-01
      • 2011-01-14
      • 1970-01-01
      • 2012-05-06
      • 2012-12-12
      相关资源
      最近更新 更多