Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "WTP Compatibility Tests"

(Web Tools Compatibility Test Information)
(Web Tools Compatibility Test Information)
Line 23: Line 23:
 
|-
 
|-
 
! Java EE
 
! Java EE
 +
!
 
!
 
!
 
* Create a Dynamic Web Project with WTP 1.5.x.
 
* Create a Dynamic Web Project with WTP 1.5.x.
Line 35: Line 36:
 
* Reopen workspace with WTP 1.5.x.
 
* Reopen workspace with WTP 1.5.x.
 
* Verify that everything appears correctly in the Project Explorer in the J2EE Perspective
 
* Verify that everything appears correctly in the Project Explorer in the J2EE Perspective
!
 
 
|
 
|
 
|-
 
|-

Revision as of 16:17, 8 February 2007

Web Tools Compatibility Test Information

WTP 1.5 <-> WTP 2.0 Background Information
  • WTP 1.5 -> WTP 2.0
  • Each team should create a test scenario to load projects or artifacts from WTP 1.5 and attempt to load, display, edit, and run them on a WTP 2.0 workspace. The links should be published here.
  • Possible coordinated compatibility JUnit which will run as part of the builds where each team can add 1.5 metadata or projects and methods to exercise their function on WTP 2.0. Java EE team has a current JUnit to be used as an example.
  • Workspace migration testing will mainly consist of a few workspaces with multiple types of content, settings, and a lot of views and perspectives open.
  • Questions remain about what exactly we need to test and we will have to gather feedback from each component team. Be wary of anything written out to settings or extension point changes.
  • WTP 2.0 -> WTP 1.5
  • We should support shared projects in a team environment where one user is on WTP 1.5 and one is on WTP 2.0, so we will need some backwards compatibility testing.


Compatibility Test Table
December 18, 2006
Component Platform(s) Compatibility Test Coverage
Java EE
  • Create a Dynamic Web Project with WTP 1.5.x.
  • Create an EJB Project with WTP 1.5.x.
  • Create an Enterprise Application Project with WTP 1.5.x.
  • Reopen workspace with WTP 2.0.
  • Verify that everything appears correctly in the Project Explorer in the J2EE Perspective
  • Create a Dynamic Web Project (2.2-2.4) with WTP 2.0.
  • Create an EJB Project (2.1) with WTP 2.0.
  • Create an Enterprise Application Project (1.2-1.4) with WTP 2.0.
  • Reopen workspace with WTP 1.5.x.
  • Verify that everything appears correctly in the Project Explorer in the J2EE Perspective
JSF
JPA

At this time it is not planned for Dali 1.0 to be backward compatible to the 0.5 tech preview release.

Server Windows or Linux
  • Create server and one or more projects in WTP 1.5.x. Include a runnable JSP, servlet, or html file.
  • Use Run on Server and make sure the web browser appears.
  • Reopen workspace with WTP 2.0.
  • Make sure the server still appears in the servers view, the project is added to the server.
  • Use Run on Server and make sure it still works.
Web Services Windows XP
  • Create top-down, bottom-up Web service and Web service client with WTP 1.5.2.
  • Open up WTP 1.5.2 workspace with WTP 2.0 driver.
    • Ensure that Web services and Web service client still works.
    • Go through creating top-down/bottom-up Web service and Web service client again on existing projects and ensure that they work.
    • Save WTP 2.0 workspace.
  • Re-open WTP 2.0 workspace in WTP 1.5.2.
    • Ensure that Web services and Web service client still works.
    • Go through creating top-down/bottom-up Web service and Web service client again on existing projects and ensure that they work.
XML and JSP Windows or Linux
  • Create Dynamic Web Project that contains a CSS, HTML, JSP, and JSPF file with WTP 1.5.x.
  • Set some properties for the files and project using the JSP Fragment and Web Content Settings Properties pages.
    • Ensure the properties are followed.
  • Set some preferences in the Structured Text Editors, CSS/DTD/HTML/JavaScript/JSP/XML Files, and Task Tags preference pages. (Include creating some templates)
    • Ensure the preferences are followed.
  • Create some snippets in the Snippets view.
    • Ensure the snippets show up in the Snippets view.
  • Open up WTP 1.5.x workspace with WTP 2.0 driver.
  • Verify changes made in the 1.5.x workspace still work in 2.0.
  • Change some preferences & properties
  • Open workspace back up in WTP 1.5.x and make sure everything still works.



Back to the Web Tools Project Main Wiki Page

Back to the top