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 254330 - Executing a setter is not modyfing the field
Summary: Executing a setter is not modyfing the field
Status: NEW
Alias: None
Product: qa
Classification: Unclassified
Component: Test Specifications (show other bugs)
Version: 8.1
Hardware: PC Windows 10 x64
: P3 normal (vote)
Assignee: issues@qa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-13 05:36 UTC by stwr
Modified: 2015-08-13 13:04 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 stwr 2015-08-13 05:36:17 UTC 
Product Version: NetBeans IDE Dev (Build 201508120002)
Java: 1.8.0_60-ea; Java HotSpot(TM) 64-Bit Server VM 25.60-b23
Runtime: Java(TM) SE Runtime Environment 1.8.0_60-ea-b25
System: Windows 10 version 10.0 running on amd64; Cp1250; pl_PL (nb)
User directory: C:\Users\Malzonek\AppData\Roaming\NetBeans\dev
Cache directory: C:\Users\Malzonek\AppData\Local\NetBeans\Cache\dev

Test Case 1 --> http://services.netbeans.org/synergy/client/app/#/case/1200/suite/1659/v/1
Test Case 2 --> http://services.netbeans.org/synergy/client/app/#/case/1201/suite/1659/v/1

I decided to open this ticket because there were two above test cases where the author expected the debugger to stop when executing setter on a field when the field breakpoint should stop on its modification.

IMO when executing the setter it is field accessing only.

However two above test cases are failing. Please decide.
Comment 1 Martin Entlicher 2015-08-13 13:04:52 UTC 
I agree that the test spec is wrong.
The 'timer' field is set only twice (lines 38 and 60), on line 194 it is accessed only.
The test passes when instead of "Field Modification" you select "Field Access".