GRECLIPSE

Groovy Test will not run in plugin versions higher than 2.0.0

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: 2.0.1Release, 2.0.2Release, 2.1.0RC1, 2.1.0RC2
  • Fix Version/s: None
  • Component/s: Testing, Running, Debugging
  • Labels:
    None
  • Environment:
    Windows XP, Eclipse 3.5
  • Testcase included:
    yes
  • Number of attachments :
    2

Description

We have a particularly long test with many static String variables initialized at the start of the test and then many test methods which uses these. When updating to newer versions from the old 2.0.0 version of the Groovy plugin, the test was no longer able to be run. The message we get is "JUnit Tests not found". Other groovy tests work just fine. Also, pulling methods out from the test into a shorter file works. It is only when we leave the lengthy test as is that it fails to run. This is not a problem with the older version of the plugin, so we guess something must have changed. I am attaching the test in question.

  1. Java Source File
    SnippetTextFormatter.java
    15/Oct/10 11:00 AM
    19 kB
    Alexis La Joie
  2. File
    SnippetTextFormatterTest.groovy
    15/Oct/10 10:58 AM
    24 kB
    Alexis La Joie

Issue Links

depends upon

Bug - A problem which impairs or prevents the functions of the product. GROOVY-4378 Incorrect handling of unicode escape sequences when calculating source locations

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
duplicates

Bug - A problem which impairs or prevents the functions of the product. GRECLIPSE-805 Unicode characters cause source locations to be off in Groovy editor

  • Major - Major loss of function.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Alexis La Joie added a comment -

Here is the Class under test.

Show
Alexis La Joie added a comment - Here is the Class under test.
Hide
Permalink
Andrew Eisenberg added a comment -

Thanks for the test case. I can see what the problem is. It is related to GROOVY-4378.

The problem is that your script uses unicode escape characters and Groovy does not handle them well. The source locations for unicode escape characters are off and this screws up the entire file.

You use one escape char here:

	private final static String KEY_NUMBER_REFERENCES =
	"<n-snippet rank=\"1\" score=\"0.1\" beginoff=\"1\" endoff=\"2\">foo\uF230bar</n-snippet>";

If you move this line to the end of the file, then source locations only for elements after that one is screwed up. So, if you do this, then you can get your tests to run.

Show
Andrew Eisenberg added a comment - Thanks for the test case. I can see what the problem is. It is related to GROOVY-4378 . The problem is that your script uses unicode escape characters and Groovy does not handle them well. The source locations for unicode escape characters are off and this screws up the entire file. You use one escape char here: private final static String KEY_NUMBER_REFERENCES = "<n-snippet rank=\" 1\ " score=\" 0.1\ " beginoff=\" 1\ " endoff=\" 2\ ">foo\uF230bar</n-snippet>" ; If you move this line to the end of the file, then source locations only for elements after that one is screwed up. So, if you do this, then you can get your tests to run.
Hide
Permalink
Andrew Eisenberg added a comment -

The problem here is unicode characters and a full description is given in GRECLIPSE-805. Fundamentally, this is a groovy compiler problem.

Show
Andrew Eisenberg added a comment - The problem here is unicode characters and a full description is given in GRECLIPSE-805 . Fundamentally, this is a groovy compiler problem.

People

  • Assignee:
    Andrew Eisenberg
    Reporter:
    Alexis La Joie
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: