Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Dali 3.3 RC1 Release"

 
(14 intermediate revisions by the same user not shown)
Line 8: Line 8:
  
 
|-
 
|-
| 408149
+
| 372286
| Missing key in jpt_jaxb_eclipselink_core_validation_description.properties
+
| switch from embedded to embedded-id causes exception and duplicate attribute overrides
| Download latest Dali build
+
| Create JPA project
| All pre-reqs and build were downloaded successfully
+
| JPA Project is created successfully
 
|-
 
|-
 
| ...
 
| ...
 
| ...
 
| ...
| Open org.eclipse.jpt.jaxb.eclipselink.core jar file from the plugins directory
+
| Create two entites as follows
| All files appear in winzip dialog
+
  @Entity
 +
public class Employee {
 +
 
 +
@Embedded
 +
private EmploymentPeriod period;
 +
}
 +
@Embeddable
 +
public class EmploymentPeriod {
 +
 
 +
private Date startDate;
 +
}
 +
| Entities are created successfully
 
|-
 
|-
 
| ...
 
| ...
 
| ...
 
| ...
| Open jpt_jaxb_eclipselink_core_validation_description.properties with wordpad
+
| Select the period attribute in the Employee entity in the JPA Structure tab
| Verify OXM_FILE__NOT_LATEST_VERSION= appears on line 18 in the .properties file
+
| period appears in the JPA details pane
 
|-
 
|-
| 408172
+
| ...
| 2.1 is default facet version for JAXB facet 
+
| ...
| Select File > New > Other
+
| Click on the mapped as link in the JPA Details pane and select Embedded ID and OK
| New dialog appears
+
| Verify period is updated and mapped as Embedded ID and no index out of bounds errors appear in Error Log.
 +
|-
 +
| 390124
 +
| JPA Content tree does not have the right items for binary type
 +
| Create JPA project
 +
| JPA project is created successfully
 
|-
 
|-
 
| ...
 
| ...
 
| ...
 
| ...
| Select JAXB > JAXB Project and click on Next button
+
| Create the Test entity as per the bug
| JAXB Project page appears and verify that 2.2 appears as the default for JAXB version
+
| Entity is created successfully and appears correctly in the Explorer pane.
 
|-
 
|-
| 408174
+
| 397765
| [EclipseLink] StringIndexOutOfBoundsException when typing new java type in oxm.xml
+
| New Entity toolbar drop-down button appearing in all perspectives instead of just JPA perspective
| Create a new JAXB EL2.5 project
+
| Make sure JPA perspective is open and Create a new JPA project
| JAXB project is created successfully
+
| JPA project is created successfully
 
|-
 
|-
 
| ...
 
| ...
 
| ...
 
| ...
| Create a new package, R-Click on New package and select EclipseLink MOXy OXM File
+
| Find the JPA Entity button on the toolbar and click on the arrow
| New EclipseLink MOXy OXM File dialog appears and oxm.xml appears as default for file name
+
| Verify the drop down menu shows JPA Entity, JPA ORM Mapping File, EclipseLink ORM Mapping File & EclipseLink Dynamic Entity
 +
|-
 +
| ...
 +
| ...
 +
| Change perspective to Java perspective
 +
| Verify JPA Entity button on the toolbar does not appear
 +
|-
 +
| ...
 +
| ...
 +
| Change perspective to web or other perspectives
 +
| Verify that JPA Entity button on the toolbar does not appear
 +
|-
 +
| ...
 +
| ...
 +
| Change perspective back to JPA
 +
| Verify JPA entity button appears on the toolbar
 +
|-
 +
| 407630
 +
| [JPA 2.0] [Validation] manytoone + ID not allowed in conjunction with an ID class.
 +
| Create JPA project
 +
| Project is created successfully
 
|-
 
|-
 
| ...
 
| ...
 
| ...
 
| ...
| Click on Finish button
+
| Create the DependentId Class per the bug
| Verify oxm.xml file is created successfully without error
+
| The Dependent class is created successfully without error
 
|-
 
|-
 
| ...
 
| ...
 
| ...
 
| ...
| Go to Source and enter blank java-type name and Save
+
| Create the Dependent entity per the bug
          <java-types>
+
| Dependent entity is created successfully and verify that the following error does not appear in the problems pane The relationship 'emp' maps an ID, which is not allowed in conjuction with an ID class.
    <java-type name=""></java-type>
+
  </java-types>
+
| Verify no errors appear in Error log
+

Latest revision as of 14:21, 12 June 2013

Dali 3.3

Dali 3.3 RC1 Release Manual Testing

Manual Testing for 3.3 RC1 Release
Bug No. Description Test Steps Test Step Results
372286 switch from embedded to embedded-id causes exception and duplicate attribute overrides Create JPA project JPA Project is created successfully
... ... Create two entites as follows
 @Entity

public class Employee {

@Embedded private EmploymentPeriod period; } @Embeddable public class EmploymentPeriod {

private Date startDate; }

Entities are created successfully
... ... Select the period attribute in the Employee entity in the JPA Structure tab period appears in the JPA details pane
... ... Click on the mapped as link in the JPA Details pane and select Embedded ID and OK Verify period is updated and mapped as Embedded ID and no index out of bounds errors appear in Error Log.
390124 JPA Content tree does not have the right items for binary type Create JPA project JPA project is created successfully
... ... Create the Test entity as per the bug Entity is created successfully and appears correctly in the Explorer pane.
397765 New Entity toolbar drop-down button appearing in all perspectives instead of just JPA perspective Make sure JPA perspective is open and Create a new JPA project JPA project is created successfully
... ... Find the JPA Entity button on the toolbar and click on the arrow Verify the drop down menu shows JPA Entity, JPA ORM Mapping File, EclipseLink ORM Mapping File & EclipseLink Dynamic Entity
... ... Change perspective to Java perspective Verify JPA Entity button on the toolbar does not appear
... ... Change perspective to web or other perspectives Verify that JPA Entity button on the toolbar does not appear
... ... Change perspective back to JPA Verify JPA entity button appears on the toolbar
407630 [JPA 2.0] [Validation] manytoone + ID not allowed in conjunction with an ID class. Create JPA project Project is created successfully
... ... Create the DependentId Class per the bug The Dependent class is created successfully without error
... ... Create the Dependent entity per the bug Dependent entity is created successfully and verify that the following error does not appear in the problems pane The relationship 'emp' maps an ID, which is not allowed in conjuction with an ID class.

Back to the top