[71cat] Background Scanning test - more information

classic Classic list List threaded Threaded
39 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Background Scanning test - more information

Jiří Kovalský
Hello folks,

    it's quite encouraging to find out that so many of you are still
open to help with testing. Thanks for that! Here are more details on it.

    As you could read in the NewAndNoteworthy72 Wiki page the indexing
infrastructure now uses transactions and prioritizing which has dramatic
impact on usability of the IDE. The project scanning and up-to-date
check do no longer block editor nor navigation. In order to test these
improvements please do the following:

1. Download latest development build [1] of NetBeans IDE 7.2
2. Use JDK 7 Update 2 or latest JDK 6 Update on Macintosh OS X.

3. Already indexed sources test
3.1 Launch IDE with --userdir parameter to point it to your existing
userdir.
3.2 IDE should start and your projects should open normally.
3.3 Make sure that code completion, syntax highlighting, code folding
and source navigation work fine.

4. Initial indexing sources test
4.1 Launch IDE with --userdir parameter to point it to a brand new userdir.
4.2 Do not import settings from previous NetBeans version.
4.3 Open all projects you typically work with.
4.4 Test usability of the IDE during indexing. Navigator should work
immediately for opened files instead of waiting for the entire scan to
be completed.
4.5 Make sure that scope of code completion, syntax highlighting, code
folding and source navigation increases after each transaction (a
scanned source root).

5. Restart after indexing test
5.1 Restart IDE after previous test.
5.2 Modify some library or subproject and verify that the change is
reflected by the IDE.

6. Write down every unexpected behavior or performance degradation and
file obvious defects to Bugzilla. Other findings send to this list.
7. Send your overall opinion about quality and performance once you are
done.

[1] http://bits.netbeans.org/download/trunk/nightly/latest

    Finally, we would appreciate it if you could finish the testing and
let us know by the end of this week. So, thank you all who find few
hours and join this effort.

Happy testing and good luck Background Scanning! :)

Best regards,
-Jirka
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

Goran Miskovic

2012/2/14 Jiří Kovalský <[hidden email]>
JDK 7 Update 2

(JDK 7 Update 2 === build 1.7.0-b147)? true : false

--
schkovich
PHP Dojo
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

Scott Palmer-3
java -version
java version "1.7.0_02"
Java(™) SE Runtime Environment (build 1.7.0_02-b13)
Java HotSpot(™) Client VM (build 22.0-b10, mixed mode, sharing)

On 2012-02-14, at 9:48 AM, Goran Miskovic wrote:


2012/2/14 Jiří Kovalský <[hidden email]>
JDK 7 Update 2

(JDK 7 Update 2 === build 1.7.0-b147)? true : false

--
schkovich
PHP Dojo

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

Jiří Kovalský
That's right. 1.7.0_02-b13 it is.

-Jirka

Dne 14.2.2012 16:12, Scott Palmer napsal(a):

> java -version
> java version "1.7.0_02"
> Java(™) SE Runtime Environment (build 1.7.0_02-b13)
> Java HotSpot(™) Client VM (build 22.0-b10, mixed mode, sharing)
>
> On 2012-02-14, at 9:48 AM, Goran Miskovic wrote:
>
>> 2012/2/14 Jiří Kovalský <[hidden email]>
>>
>>     JDK 7 Update 2
>>
>> (JDK 7 Update 2 === build 1.7.0-b147)? true : false
>>
>> --
>> schkovich
>> PHP Dojo <http://phpdojo.blogspot.com/>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

Goran Miskovic

2012/2/14 Jiří Kovalský <[hidden email]>
That's right. 1.7.0_02-b13 it is.

Updated.  :)

java -version 
java version "1.7.0_02"
Java(TM) SE Runtime Environment (build 1.7.0_02-b13)
Java HotSpot(TM) 64-Bit Server VM (build 22.0-b10, mixed mode)

--
schkovich
PHP Dojo
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

Alied Pérez Martínez
In reply to this post by Jiří Kovalský
http://netbeans.org/bugzilla/show_bug.cgi?id=208399
testing will continue soon.

On 2/14/2012 11:05 AM, Jiří Kovalský wrote:

> Hello folks,
>
>    it's quite encouraging to find out that so many of you are still
> open to help with testing. Thanks for that! Here are more details on it.
>
>    As you could read in the NewAndNoteworthy72 Wiki page the indexing
> infrastructure now uses transactions and prioritizing which has
> dramatic impact on usability of the IDE. The project scanning and
> up-to-date check do no longer block editor nor navigation. In order to
> test these improvements please do the following:
>
> 1. Download latest development build [1] of NetBeans IDE 7.2
> 2. Use JDK 7 Update 2 or latest JDK 6 Update on Macintosh OS X.
>
> 3. Already indexed sources test
> 3.1 Launch IDE with --userdir parameter to point it to your existing
> userdir.
> 3.2 IDE should start and your projects should open normally.
> 3.3 Make sure that code completion, syntax highlighting, code folding
> and source navigation work fine.
>
> 4. Initial indexing sources test
> 4.1 Launch IDE with --userdir parameter to point it to a brand new
> userdir.
> 4.2 Do not import settings from previous NetBeans version.
> 4.3 Open all projects you typically work with.
> 4.4 Test usability of the IDE during indexing. Navigator should work
> immediately for opened files instead of waiting for the entire scan to
> be completed.
> 4.5 Make sure that scope of code completion, syntax highlighting, code
> folding and source navigation increases after each transaction (a
> scanned source root).
>
> 5. Restart after indexing test
> 5.1 Restart IDE after previous test.
> 5.2 Modify some library or subproject and verify that the change is
> reflected by the IDE.
>
> 6. Write down every unexpected behavior or performance degradation and
> file obvious defects to Bugzilla. Other findings send to this list.
> 7. Send your overall opinion about quality and performance once you
> are done.
>
> [1] http://bits.netbeans.org/download/trunk/nightly/latest
>
>    Finally, we would appreciate it if you could finish the testing and
> let us know by the end of this week. So, thank you all who find few
> hours and join this effort.
>
> Happy testing and good luck Background Scanning! :)
>
> Best regards,
> -Jirka

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

Pavel Selivanov
In reply to this post by Jiří Kovalský

6. Write down every unexpected behavior or performance degradation and file obvious defects to Bugzilla. Other findings send to this list.

Syntax highlightning for css files not working while scanning in progress.

Report here: http://netbeans.org/bugzilla/show_bug.cgi?id=208409


7. Send your overall opinion about quality and performance once you are done.

Will test for some days with different jdk's.


--
С уважением, Селиванов Павел.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

Javier Ortiz
In reply to this post by Jiří Kovalský
Results:

3- Pass
4- Pass
5- Fail
6- N/A
7- overall the IDE seemed lot faster on start up. Great work! Pretty smooth for plain java projects. I even opened my big RCP application, opening all required projects, a mix of modules and plain java projects, 23 in total without a delay. That took up to a minute before (maybe more). My web project (with dependent plain Java projects) without issues either.

This change will make MANY people happy. This is a huge crowd pleaser!

Senior Software Quality Engineer
ArthroCare Corporation
7000 William Cannon Drive
Austin, TX 78735
Phone: 512-358-5996
email: [hidden email]

-----Original Message-----
From: Jiří Kovalský [mailto:[hidden email]]
Sent: Tuesday, February 14, 2012 8:05 AM
To: NetCAT team
Subject: [71cat] Background Scanning test - more information

Hello folks,

    it's quite encouraging to find out that so many of you are still
open to help with testing. Thanks for that! Here are more details on it.

    As you could read in the NewAndNoteworthy72 Wiki page the indexing
infrastructure now uses transactions and prioritizing which has dramatic
impact on usability of the IDE. The project scanning and up-to-date
check do no longer block editor nor navigation. In order to test these
improvements please do the following:

1. Download latest development build [1] of NetBeans IDE 7.2
2. Use JDK 7 Update 2 or latest JDK 6 Update on Macintosh OS X.

3. Already indexed sources test
3.1 Launch IDE with --userdir parameter to point it to your existing
userdir.
3.2 IDE should start and your projects should open normally.
3.3 Make sure that code completion, syntax highlighting, code folding
and source navigation work fine.

4. Initial indexing sources test
4.1 Launch IDE with --userdir parameter to point it to a brand new userdir.
4.2 Do not import settings from previous NetBeans version.
4.3 Open all projects you typically work with.
4.4 Test usability of the IDE during indexing. Navigator should work
immediately for opened files instead of waiting for the entire scan to
be completed.
4.5 Make sure that scope of code completion, syntax highlighting, code
folding and source navigation increases after each transaction (a
scanned source root).

5. Restart after indexing test
5.1 Restart IDE after previous test.
5.2 Modify some library or subproject and verify that the change is
reflected by the IDE.

6. Write down every unexpected behavior or performance degradation and
file obvious defects to Bugzilla. Other findings send to this list.
7. Send your overall opinion about quality and performance once you are
done.

[1] http://bits.netbeans.org/download/trunk/nightly/latest

    Finally, we would appreciate it if you could finish the testing and
let us know by the end of this week. So, thank you all who find few
hours and join this effort.

Happy testing and good luck Background Scanning! :)

Best regards,
-Jirka
**********

The information contained in this e-mail message, together with any
attachments thereto, is intended only for the personal and confidential
use of the addressee named above. The message and the attachments
 are or may be privileged or protected communication. If you are not the
intended recipient of this message, or authorized to receive it for the
intended recipient, you have received this message in error, and you
are not to review, use, disseminate, distribute or copy this message,
any attachments thereto, or their contents. If you have received this
message in error, please immediately notify us by return e-mail
message, and delete the original message.

Pursuant to Circular 230 issued by the United States Treasury
Department and relating to practice before the Internal Revenue
Services, any comment or opinion in this communication relating to a
federal tax issue is not intended to be used, and cannot be used, by a
taxpayer for the purpose of avoiding tax-related penalties that may be
imposed on the taxpayer.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

Alied Pérez Martínez
In reply to this post by Alied Pérez Martínez
At night I'll try it with bigger projects and in Linux.

On 2/14/2012 12:58 PM, alied wrote:
> http://netbeans.org/bugzilla/show_bug.cgi?id=208399
> testing will continue soon.
>
> On 2/14/2012 11:05 AM, Jiří Kovalský wrote:
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

medeag
Unfortunately I have no time to test these test cases: 

But just out of curiosity i have tried first point for 5 mins, one thing i noticed i had opened one project and while scan was is in progress tried to run another project and got: please wait, classpath scan in progress... is it correct behavior?  

Thanks,
Medea

2012/2/15 alied <[hidden email]>
At night I'll try it with bigger projects and in Linux.


On 2/14/2012 12:58 PM, alied wrote:
http://netbeans.org/bugzilla/show_bug.cgi?id=208399
testing will continue soon.

On 2/14/2012 11:05 AM, Jiří Kovalský wrote:

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

David Strupl-3
Hello,

On Feb 15, 2012, at 7:23 AM, Medea Gugushvili wrote:

Unfortunately I have no time to test these test cases: 

But just out of curiosity i have tried first point for 5 mins, one thing i noticed i had opened one project and while scan was is in progress tried to run another project and got: please wait, classpath scan in progress... is it correct behavior?  

If the project you are trying to run has compile on save feature on it is correct behaviour. If it is turned off for that project it is a bug.

Br,

David



Thanks,
Medea

2012/2/15 alied <[hidden email]>
At night I'll try it with bigger projects and in Linux.


On 2/14/2012 12:58 PM, alied wrote:
http://netbeans.org/bugzilla/show_bug.cgi?id=208399
testing will continue soon.

On 2/14/2012 11:05 AM, Jiří Kovalský wrote:


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

William Bacchi
In reply to this post by Jiří Kovalský
I tried points 3 on windows xp an they seem ok, but I also experienced
the behaviour indicated by Medea.

Point 4.3 I get

java.lang.NullPointerException: Null group for name=form
     at
org.netbeans.core.windows.PersistenceHandler.groupConfigRemoved(PersistenceHandler.java:953)
     at
org.netbeans.core.windows.persistence.ModuleChangeHandler$5.run(ModuleChangeHandler.java:537)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
     at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:705)
     at java.awt.EventQueue.access$000(EventQueue.java:101)
     at java.awt.EventQueue$3.run(EventQueue.java:666)
     at java.awt.EventQueue$3.run(EventQueue.java:664)
     at java.security.AccessController.doPrivileged(Native Method)
     at
java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:675)
     at
org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:162)
     at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:211)
     at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:128)
     at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:117)
     at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:113)
     at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:105)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:90)

when opening project and the project in projects navigator is shown like
in the Files navigator.

If I close and reopen the project I get several slowness detected but
then the Projects view is correct and I correctly see a missing server
problem.

Greetings, William.

Il 14/02/2012 15.05, Jiří Kovalský ha scritto:

> Hello folks,
>
>    it's quite encouraging to find out that so many of you are still
> open to help with testing. Thanks for that! Here are more details on it.
>
>    As you could read in the NewAndNoteworthy72 Wiki page the indexing
> infrastructure now uses transactions and prioritizing which has
> dramatic impact on usability of the IDE. The project scanning and
> up-to-date check do no longer block editor nor navigation. In order to
> test these improvements please do the following:
>
> 1. Download latest development build [1] of NetBeans IDE 7.2
> 2. Use JDK 7 Update 2 or latest JDK 6 Update on Macintosh OS X.
>
> 3. Already indexed sources test
> 3.1 Launch IDE with --userdir parameter to point it to your existing
> userdir.
> 3.2 IDE should start and your projects should open normally.
> 3.3 Make sure that code completion, syntax highlighting, code folding
> and source navigation work fine.
>
> 4. Initial indexing sources test
> 4.1 Launch IDE with --userdir parameter to point it to a brand new
> userdir.
> 4.2 Do not import settings from previous NetBeans version.
> 4.3 Open all projects you typically work with.
> 4.4 Test usability of the IDE during indexing. Navigator should work
> immediately for opened files instead of waiting for the entire scan to
> be completed.
> 4.5 Make sure that scope of code completion, syntax highlighting, code
> folding and source navigation increases after each transaction (a
> scanned source root).
>
> 5. Restart after indexing test
> 5.1 Restart IDE after previous test.
> 5.2 Modify some library or subproject and verify that the change is
> reflected by the IDE.
>
> 6. Write down every unexpected behavior or performance degradation and
> file obvious defects to Bugzilla. Other findings send to this list.
> 7. Send your overall opinion about quality and performance once you
> are done.
>
> [1] http://bits.netbeans.org/download/trunk/nightly/latest
>
>    Finally, we would appreciate it if you could finish the testing and
> let us know by the end of this week. So, thank you all who find few
> hours and join this effort.
>
> Happy testing and good luck Background Scanning! :)
>
> Best regards,
> -Jirka

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

William Bacchi
In reply to this post by David Strupl-3
The project I tried has compile on save on.

Greetings, William.

Il 15/02/2012 8.49, David Strupl ha scritto:
Hello,

On Feb 15, 2012, at 7:23 AM, Medea Gugushvili wrote:

Unfortunately I have no time to test these test cases: 

But just out of curiosity i have tried first point for 5 mins, one thing i noticed i had opened one project and while scan was is in progress tried to run another project and got: please wait, classpath scan in progress... is it correct behavior?  

If the project you are trying to run has compile on save feature on it is correct behaviour. If it is turned off for that project it is a bug.

Br,

David



Thanks,
Medea

2012/2/15 alied <[hidden email]>
At night I'll try it with bigger projects and in Linux.


On 2/14/2012 12:58 PM, alied wrote:
http://netbeans.org/bugzilla/show_bug.cgi?id=208399
testing will continue soon.

On 2/14/2012 11:05 AM, Jiří Kovalský wrote:



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

Jiří Kovalský
In reply to this post by William Bacchi
Which is an already known issue:
http://netbeans.org/bugzilla/show_bug.cgi?id=208388

Thanks Wiliam,
-Jirka

Dne 15.2.2012 09:04, Wiliam Bacchi napsal(a):

> I tried points 3 on windows xp an they seem ok, but I also experienced
> the behaviour indicated by Medea.
>
> Point 4.3 I get
>
> java.lang.NullPointerException: Null group for name=form
> at
> org.netbeans.core.windows.PersistenceHandler.groupConfigRemoved(PersistenceHandler.java:953)
>
> at
> org.netbeans.core.windows.persistence.ModuleChangeHandler$5.run(ModuleChangeHandler.java:537)
>
> at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:705)
> at java.awt.EventQueue.access$000(EventQueue.java:101)
> at java.awt.EventQueue$3.run(EventQueue.java:666)
> at java.awt.EventQueue$3.run(EventQueue.java:664)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
>
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:675)
> at
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:162)
>
> at
> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:211)
>
> at
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:128)
>
> at
> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:117)
>
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:113)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:105)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
>
> when opening project and the project in projects navigator is shown like
> in the Files navigator.

[snip]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

Hermien Pellissier
In reply to this post by Jiří Kovalský
Hi,

I tested briefly on Windows 7, working with two chained NetBeans platform suites with lots of modules each. Everything worked very smoothly. No exceptions or other unexpected behaviour. And most definitely a great improvement in user experience! :)

Best wishes,
Hermien PELLISSIER



On Tue, Feb 14, 2012 at 4:05 PM, Jiří Kovalský <[hidden email]> wrote:
Hello folks,

  it's quite encouraging to find out that so many of you are still open to help with testing. Thanks for that! Here are more details on it.

  As you could read in the NewAndNoteworthy72 Wiki page the indexing infrastructure now uses transactions and prioritizing which has dramatic impact on usability of the IDE. The project scanning and up-to-date check do no longer block editor nor navigation. In order to test these improvements please do the following:

1. Download latest development build [1] of NetBeans IDE 7.2
2. Use JDK 7 Update 2 or latest JDK 6 Update on Macintosh OS X.

3. Already indexed sources test
3.1 Launch IDE with --userdir parameter to point it to your existing userdir.
3.2 IDE should start and your projects should open normally.
3.3 Make sure that code completion, syntax highlighting, code folding and source navigation work fine.

4. Initial indexing sources test
4.1 Launch IDE with --userdir parameter to point it to a brand new userdir.
4.2 Do not import settings from previous NetBeans version.
4.3 Open all projects you typically work with.
4.4 Test usability of the IDE during indexing. Navigator should work immediately for opened files instead of waiting for the entire scan to be completed.
4.5 Make sure that scope of code completion, syntax highlighting, code folding and source navigation increases after each transaction (a scanned source root).

5. Restart after indexing test
5.1 Restart IDE after previous test.
5.2 Modify some library or subproject and verify that the change is reflected by the IDE.

6. Write down every unexpected behavior or performance degradation and file obvious defects to Bugzilla. Other findings send to this list.
7. Send your overall opinion about quality and performance once you are done.

[1] http://bits.netbeans.org/download/trunk/nightly/latest

  Finally, we would appreciate it if you could finish the testing and let us know by the end of this week. So, thank you all who find few hours and join this effort.

Happy testing and good luck Background Scanning! :)

Best regards,
-Jirka

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

medeag
In reply to this post by William Bacchi
same here, so not an issue :)

2012/2/15 Wiliam Bacchi <[hidden email]>
The project I tried has compile on save on.

Greetings, William.

Il 15/02/2012 8.49, David Strupl ha scritto:
Hello,

On Feb 15, 2012, at 7:23 AM, Medea Gugushvili wrote:

Unfortunately I have no time to test these test cases: 

But just out of curiosity i have tried first point for 5 mins, one thing i noticed i had opened one project and while scan was is in progress tried to run another project and got: please wait, classpath scan in progress... is it correct behavior?  

If the project you are trying to run has compile on save feature on it is correct behaviour. If it is turned off for that project it is a bug.

Br,

David



Thanks,
Medea

2012/2/15 alied <[hidden email]>
At night I'll try it with bigger projects and in Linux.


On 2/14/2012 12:58 PM, alied wrote:
http://netbeans.org/bugzilla/show_bug.cgi?id=208399
testing will continue soon.

On 2/14/2012 11:05 AM, Jiří Kovalský wrote:




Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

Javier Ortiz

I created this report from the IDE: #560773. It was a file not found exception during project scanning. Worth taking a look.

 

 

Senior Software Quality Engineer

ArthroCare Corporation

7000 William Cannon Drive

Austin, TX 78735

Phone: 512-358-5996

email: [hidden email]

**********

The information contained in this e-mail message, together with any
attachments thereto, is intended only for the personal and confidential
use of the addressee named above. The message and the attachments
are or may be privileged or protected communication. If you are not the
intended recipient of this message, or authorized to receive it for the
intended recipient, you have received this message in error, and you
are not to review, use, disseminate, distribute or copy this message,
any attachments thereto, or their contents. If you have received this
message in error, please immediately notify us by return e-mail
message, and delete the original message.

Pursuant to Circular 230 issued by the United States Treasury
Department and relating to practice before the Internal Revenue
Services, any comment or opinion in this communication relating to a
federal tax issue is not intended to be used, and cannot be used, by a
taxpayer for the purpose of avoiding tax-related penalties that may be
imposed on the taxpayer.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

Wilfling Stefan
In reply to this post by Jiří Kovalský
Hi!

>3.3 Make sure that code completion, syntax highlighting, code folding and source navigation work fine.
While testing a big java-source-file, the following Exception occured:
->  http://netbeans.org/bugzilla/show_bug.cgi?id=208381

Some minutes later an OutOfMemoryError occured:
-> http://netbeans.org/bugzilla/show_bug.cgi?id=208501

PageUp/PageDown is slow at big java-source-files while Scanning
-> http://netbeans.org/bugzilla/show_bug.cgi?id=208507

> 4.4 Test usability of the IDE during indexing. Navigator should work immediately for opened files instead of waiting for the entire scan to be completed.
Ctrl-R works while scanning at private class-variable.
Ctrl-R doesn´t works while scanning at protected class-variable. -> I think that´s OK, or?

I tried "Collapse ALL" while while Scanning-Projects:
->Exception http://netbeans.org/bugzilla/show_bug.cgi?id=208283

> 7. Send your overall opinion about quality and performance once you are done.
It´s really faster at startup and it make´s fun to work while Scanning-Projects.
Good job!


Mit freundlichen Grüssen
 
________________________________________________________________________
 
Wilfling Stefan
 
SOFTLINE Datenverarbeitungsgesellschaft mbH
Ungerdorf 116
A - 8200 Gleisdorf
 
Tel:  +43 (0) 3112 / 3304 - 17
Fax: +43 (0) 3112 / 7020 - 17
 
http://www.softline.at
[hidden email]

-----Ursprüngliche Nachricht-----
Von: Jiří Kovalský [mailto:[hidden email]]
Gesendet: Dienstag, 14. Februar 2012 15:05
An: NetCAT team
Betreff: [71cat] Background Scanning test - more information

Hello folks,

    it's quite encouraging to find out that so many of you are still open to help with testing. Thanks for that! Here are more details on it.

    As you could read in the NewAndNoteworthy72 Wiki page the indexing infrastructure now uses transactions and prioritizing which has dramatic impact on usability of the IDE. The project scanning and up-to-date check do no longer block editor nor navigation. In order to test these improvements please do the following:

1. Download latest development build [1] of NetBeans IDE 7.2 2. Use JDK 7 Update 2 or latest JDK 6 Update on Macintosh OS X.

3. Already indexed sources test
3.1 Launch IDE with --userdir parameter to point it to your existing userdir.
3.2 IDE should start and your projects should open normally.
3.3 Make sure that code completion, syntax highlighting, code folding and source navigation work fine.

4. Initial indexing sources test
4.1 Launch IDE with --userdir parameter to point it to a brand new userdir.
4.2 Do not import settings from previous NetBeans version.
4.3 Open all projects you typically work with.
4.4 Test usability of the IDE during indexing. Navigator should work immediately for opened files instead of waiting for the entire scan to be completed.
4.5 Make sure that scope of code completion, syntax highlighting, code folding and source navigation increases after each transaction (a scanned source root).

5. Restart after indexing test
5.1 Restart IDE after previous test.
5.2 Modify some library or subproject and verify that the change is reflected by the IDE.

6. Write down every unexpected behavior or performance degradation and file obvious defects to Bugzilla. Other findings send to this list.
7. Send your overall opinion about quality and performance once you are done.

[1] http://bits.netbeans.org/download/trunk/nightly/latest

    Finally, we would appreciate it if you could finish the testing and let us know by the end of this week. So, thank you all who find few hours and join this effort.

Happy testing and good luck Background Scanning! :)

Best regards,
-Jirka
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

Angelo Quaglia
In reply to this post by Jiří Kovalský
Hi,
I have been using NetBeans Dev 201202150400 for my everyday work (Java, Maven) and it works fine.
Usability has increased a lot.
Many thanks.

Best regards,
Angelo


2012/2/14 Jiří Kovalský <[hidden email]>
Hello folks,

  it's quite encouraging to find out that so many of you are still open to help with testing. Thanks for that! Here are more details on it.

  As you could read in the NewAndNoteworthy72 Wiki page the indexing infrastructure now uses transactions and prioritizing which has dramatic impact on usability of the IDE. The project scanning and up-to-date check do no longer block editor nor navigation. In order to test these improvements please do the following:

1. Download latest development build [1] of NetBeans IDE 7.2
2. Use JDK 7 Update 2 or latest JDK 6 Update on Macintosh OS X.

3. Already indexed sources test
3.1 Launch IDE with --userdir parameter to point it to your existing userdir.
3.2 IDE should start and your projects should open normally.
3.3 Make sure that code completion, syntax highlighting, code folding and source navigation work fine.

4. Initial indexing sources test
4.1 Launch IDE with --userdir parameter to point it to a brand new userdir.
4.2 Do not import settings from previous NetBeans version.
4.3 Open all projects you typically work with.
4.4 Test usability of the IDE during indexing. Navigator should work immediately for opened files instead of waiting for the entire scan to be completed.
4.5 Make sure that scope of code completion, syntax highlighting, code folding and source navigation increases after each transaction (a scanned source root).

5. Restart after indexing test
5.1 Restart IDE after previous test.
5.2 Modify some library or subproject and verify that the change is reflected by the IDE.

6. Write down every unexpected behavior or performance degradation and file obvious defects to Bugzilla. Other findings send to this list.
7. Send your overall opinion about quality and performance once you are done.

[1] http://bits.netbeans.org/download/trunk/nightly/latest

  Finally, we would appreciate it if you could finish the testing and let us know by the end of this week. So, thank you all who find few hours and join this effort.

Happy testing and good luck Background Scanning! :)

Best regards,
-Jirka

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[71cat] Re: Background Scanning test - more information

Jiří Kovalský
In reply to this post by Jiří Kovalský
Thank you all for your very useful bug reports and investigations! It
looks like nothing critical was found which is very nice. We are also
glad that majority of you noticed the improvement in usability.

Is there anybody who didn't have time for the test yet and still plans
to take a look at background scanning over the weekend?

Thanks a lot again,
-Jirka

Dne 14.2.2012 15:05, Jiří Kovalský napsal(a):

> Hello folks,
>
> it's quite encouraging to find out that so many of you are still open to
> help with testing. Thanks for that! Here are more details on it.
>
> As you could read in the NewAndNoteworthy72 Wiki page the indexing
> infrastructure now uses transactions and prioritizing which has dramatic
> impact on usability of the IDE. The project scanning and up-to-date
> check do no longer block editor nor navigation. In order to test these
> improvements please do the following:
>
> 1. Download latest development build [1] of NetBeans IDE 7.2
> 2. Use JDK 7 Update 2 or latest JDK 6 Update on Macintosh OS X.
>
> 3. Already indexed sources test
> 3.1 Launch IDE with --userdir parameter to point it to your existing
> userdir.
> 3.2 IDE should start and your projects should open normally.
> 3.3 Make sure that code completion, syntax highlighting, code folding
> and source navigation work fine.
>
> 4. Initial indexing sources test
> 4.1 Launch IDE with --userdir parameter to point it to a brand new userdir.
> 4.2 Do not import settings from previous NetBeans version.
> 4.3 Open all projects you typically work with.
> 4.4 Test usability of the IDE during indexing. Navigator should work
> immediately for opened files instead of waiting for the entire scan to
> be completed.
> 4.5 Make sure that scope of code completion, syntax highlighting, code
> folding and source navigation increases after each transaction (a
> scanned source root).
>
> 5. Restart after indexing test
> 5.1 Restart IDE after previous test.
> 5.2 Modify some library or subproject and verify that the change is
> reflected by the IDE.
>
> 6. Write down every unexpected behavior or performance degradation and
> file obvious defects to Bugzilla. Other findings send to this list.
> 7. Send your overall opinion about quality and performance once you are
> done.
>
> [1] http://bits.netbeans.org/download/trunk/nightly/latest
>
> Finally, we would appreciate it if you could finish the testing and let
> us know by the end of this week. So, thank you all who find few hours
> and join this effort.
>
> Happy testing and good luck Background Scanning! :)
>
> Best regards,
> -Jirka
12
Loading...