This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 270822 - Netbeans refactoring Must support (Groovy) Unit Test code
Summary: Netbeans refactoring Must support (Groovy) Unit Test code
Status: NEW
Alias: None
Product: ide
Classification: Unclassified
Component: Code (show other bugs)
Version: 8.2
Hardware: All Windows 10
: P3 normal (vote)
Assignee: issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-07 01:37 UTC by aplatypus
Modified: 2017-06-07 01:37 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description aplatypus 2017-06-07 01:37:08 UTC 
Product Version = NetBeans IDE 8.2 (Build 201609300101)
Operating System = Windows 10 version 10.0 running on amd64
Java; VM; Vendor = 1.8.0_131
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.131-b11

Reproducibility: Happens every time

STEPS:
  * Establish a simple Unit Test script using a Groovy test class (e.g. Junit or Spock)
  * Use an existing Java class in the unit test  e.g Target.Java
  * Ensure unit test is PASSING
  * Carry out simple refactoring of a class -- Rename the  existing Target.java Java class
  * Refactoring will carry-out renaming of class and update import statements, etc.
  * Run the unit test after the renaming.

ACTUAL:

  # Test fails because of compiler/syntax errors

EXPECTED:
  --> Passing test should PASS 
         * Testing should not fail due to supported  refactoring changes

The value of refactoring code is severly discounted when the test cases need to be manually checked and validated by hand.