Please use the Apache issue tracking system for new NetBeans issues (https://issues.apache.org/jira/projects/NETBEANS0/issues) !!
Bug 93633 - Need to migrate the automation tests into the NB opensource CVS as well
Need to migrate the automation tests into the NB opensource CVS as well
Status: VERIFIED FIXED
Product: obsolete
Classification: Unclassified
Component: visualweb
5.x
All Mac OS X
: P2 (vote)
: TBD
Assigned To: Ch Nguyen
issues@obsolete
:
Depends on:
Blocks: 90449
  Show dependency treegraph
 
Reported: 2007-01-31 02:04 UTC by Ch Nguyen
Modified: 2007-04-27 22:58 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ch Nguyen 2007-01-31 02:04:53 UTC
Need to opensource the Visual Web tests as well.

Here is a summary of the first meeting we had on this topic (notes taken by Lark):
Issue: There is a 3 deep directory limitation on netbeans modules.
Test infrastructure is not a netbeans module so this limitation may not apply
(AI: verify with NB QE)

Gave short description of rave test structure

Looked at netbeans structure
http://www.netbeans.org/source/browse/web/
AI: Find out from martin if it matters where test dir is (all together) or does
it have to be at the module level)

Tasks
1. Define a new module structure
2. Match current directory structure with an owner (consult with shura)
3. Cleanup obsolete files
4. Change Package structure
5. update licenses (script for doing this)
6. Clean up (scrub) code (Tool from ibm, see opensource twiki for link)

Priorities
1. Get buy-in on structure
2. add test dir in visual web sandbox
3. re-package gravy (keep name or change it) org.netbeans.module.visualweb.gravy?
4. migrate xtest structure & sanity test

Goal
To have sanity running for NB Milestone 7 (2/15). Get gravy cleansed,
repackaged, licensed and migrated this week.

Followon activities
1. Migrate rest of automation. Most likely this will be handled by the 'owners'
which has yet to be 100% defined.

Meet again next week for status.
Comment 1 Ch Nguyen 2007-02-05 19:07:23 UTC
A summary of this week's follow up meeting:
Attendees: Sherry, Shura, Alexey, JimB, Chau

.  Shura explained the way the new package name for gravy should be since it
should be just like jellytools in NB.
.  Alexey will go through the table in the QE's Migration Plan document and make
sure all the entries there are correct, especially with the new package names.
.  JimB will run through his tool again once the information in the table is
updated.  JimB and Alexey will get it to work with NB 5.5 (release55_vwpack
branch).  JimB will provide a test.zip.
.  Alexey will go though the refactored test and fix up the test directory
structure as specified in QE Migration plan, such as moving the functional test
to the module directories, etc.  and the test (especially santity test) still works.
.  Will first integrate into the release60_vw branch.  Alexey will let Chau know
if he needs help integrating the test into this branch
.  Chau will merge release60_vw branch into trunk by the end of this week.
.  All tests should be migrated into NB CVS and minimal sanity test can be
available for M7.
Comment 2 Ch Nguyen 2007-02-12 16:23:56 UTC
Alexey Butenko wrote:

> Hi Chau,
>
> I've commented it for now. And removed test cases from sanity which are
checking non existing yet functionality,
> i.e. double click on button and creating event handler for component, and now
scenario looks like following:
>
> testAddApplocationServer:
>    - Add Glassfish Application Server (server data taken from
DefaultDeploymentTargets.properties)
> testCreateProject:
>    - Create J2EE 1.4 project
> testAddButton:
>    - Add button, set its text property to "GO"
>    - Open JSP editor, verify that text property is set
> testPageNavigation:
>    - Open Page Navigation
>    - Add second page via Add Page context menu
>    - Make link with name 'go' from page1 to page2
> testCloseProject:
>    - Close Project
> testCreateJavaEE5Project:
>    - Create Java EE 5 project
> testAddComponents:
>    - Add label, set its text property to 'Java EE 5 Project'
>    - Add button, set its text property to 'Push me'
> testExecution:
>    - Deploy project
>    - Press button via HttpUnit and verify that page has not changed
>
> It is 87.50% successful now, with 1 error, which is product issue.




Comment 3 Ch Nguyen 2007-02-13 07:05:24 UTC
How to build and run the sanity test by Sherry Zhou:

After visual web build, you need to do following things:
1. Check out the netbeans modules used by sanity. They are
 core/external
 nbbuild
 unit/external
 testtools/external
 xtest
 jemmy
 jellytools


2. Build  xtest
    cd xtest; ant  makedist-simple -Dnetbeans.dest.dir="my_IDE_dir"

3. Build gravy jar
   cd webvisual/gravy
   ant jar

4. Specify glassfish location, same as we did for shortfin
   cd visualweb/test/data
   cp DefaultDeploymentTargets.property.template DefaultDeploymentTargets.property
   Specify glassfish location in DefaultDeploymentTargets.property.

6. Run sanity
    cd visualweb/test
   ant sanitytests
Comment 4 Sherry Zhou 2007-02-13 21:57:28 UTC
There are some typo in previous instructions.  Please ignore it. Here is
corrected one.

After visual web build, you need to do following things:
1. Check out the netbeans modules used by sanity. They are
 core/external
 nbbuild
 junit/external
 testtools/external
 xtest
 jemmy
 jellytools


2. Build  xtest
    cd xtest; ant  makedist-simple -Dnetbeans.dest.dir="my_IDE_dir"

3. Build gravy jar
   cd  visualweb/gravy
   ant jar

4. Specify glassfish location, same as we did for shortfin
   cd visualweb/test/data
   cp DefaultDeploymentTargets.property.template DefaultDeploymentTargets.property
   Specify glassfish location in DefaultDeploymentTargets.property.

6. Run sanity
   cd visualweb/test
   ant sanitytests
Comment 5 Lark Fitzgerald 2007-04-27 22:58:48 UTC
sanity is open.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo