Uploaded image for project: 'Maven Surefire'
  1. Maven Surefire
  2. SUREFIRE-1390

maven-failsafe-plugin:2.20:verify classNotFound (spring autowired service) testNg

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Invalid
    • 2.19, 2.19.1, 2.20
    • None
    • Maven Failsafe Plugin, TestNG support
    • Win 10; terminal: MINGW64; Spring boot starter [1.5.3, 1.5.4]

    Description

      Apologies in advance if duplicate or needs to be in Failsafe specific project, am new to jira, tried searching, but couldn't find match. Not sure if bug in plugin, but couldn't find anything on google/SO based on failsafe stacktrace.

      Upgrading failsafe versions to [2.19, 2.20] causes unexpected failure during integration test run of spring-based testNg tests.

      However, remaining on current failsafe version, 2.18.1, works as expected.

      See attachments for more details.

      Attachments

        1. 2017-07-12T09-45-33_517-jvmRun1.dump
          5 kB
          hhwebdev
        2. cmd_mvn_install_X.txt
          13 kB
          hhwebdev
        3. failsafe-summary.xml
          3 kB
          hhwebdev

        Activity

          People

            tibordigana Tibor Digana
            hhwebdev hhwebdev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: