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

Dali 3.2 M6

Revision as of 09:51, 13 March 2012 by Unnamed Poltroon (Talk)

Dali 3.2

Dali 3.2 M6 Release Manual Testing

Manual Testing for 3.2 M6 Release
Bug No. Description Test Steps Test Step Results
277017 class chooser widgets don't work if package is set in orm.xml Create JPA 2.0 Generic project JPA Project is created successfully
... ... Create JPA Entity Entity is created successfully
... ... Create JPA ORM mapping file and add JPA Entity to mapping file via the editor
    <package>model</package>
    <entity class="Address"></entity>
Entity is added to mapping file successfully
... ... Select the JPA Entity in the orm mapping file, then click on Java Class in the JPA Details pane Verify the JPA Entity editor window opens(appears) and the JPA Details appears so you can edit the entity.
... ... Open the .class files in Comment #6 of the bug Verify they have been updated with String
305591 mappedBy choices should not include transient mappings Create JPA project, create 2 JPA Entities (Address, Employee) with at least 3 or 4 attributes JPA Project and entities are created successfully
... ... Map an attribute in the Employee entity as one-to-one and adjust any errors Mapping as one-to-one is successful without error
... ... Add the JPA ORM Mapping file to the project ORM Mapping file is added successfully
... ... Add the Employee Entity to the orm mapping file Employee Entity is added successfully
... ... Add the attribute that you mapped as one-to-one to the orm mapping file Attribute is added to orm mapping file successfully
... ... In the Joining Strategy section in JPA Details pane select Mapped By radio button and click on the Attribute drop down Verify all items appear from the mapped table
... ... Go back to the Address entity and change one of the attributes to mapped as @Tranisient, then go back to the attribute field in the JPA Details for the orm mapping file Verify the attribute that is now transient does not appear in the drop down list
368393 Add converter button is disabled for entity-mappings Create JPA EclipseLink project. Project is created successfully
... ... R-Click on the project and select New>EclipseLink orm mapping file New EclipseLink Mapping File dialog appears
... ... Leave the defaults and click on Finish. EclipseLink ORM Mapping file is created successfully
... ... Select mapping file Entity Mappings in the JPA Structure Pane and Expand Converters section in the JPA Details pane Verify the Add button is enabled and you can add a converter as well as remove a converter
... ... Add a JPA Entity to the project and then Add that Entity to the EL orm mapping file Entity is added to mapping file successfully
... ... Select the Entity within the Mapping file JPA STructure pane and Expand Converters section in the JPA Details pane Verify the Add button is enabled and you can add a converter as well as remove a converter
369944 [EclipseLink] dynamic persistence and extensible entities validation for attribute-type Create JPA EclipseLink project, Create JPA Entity with 2 or 3 attributes, Create EclipseLink ORM mapping file Project, Entity and mapping file are created successfully
... ... Add the entity and one of the attributes to the EL Mapping file and add the following to the eclipselink-orm.xml editor and then Save.
    <attributes>
        <basic name="City" access="VIRTUAL">
        </basic>
    </attributes>
Verify the following validation error appears in the problems pane Virtual attribute "City" must specify an attribute-type
... ... Add attribute-type="test" after "VIRTUAL" in the editor and Save Verify the following validation error appears in the problems pane Attribute type "test" does not exist.
370342 partial package in the package element should not be supported in the orm.xml Create a JPA Generic project, Create JPA Entity (package = foo.com.model, Name = Employee), Create JPA orm mapping file Project, Entity and orm mapping file are all created successfully
... ... Add the following Entity to the orm mapping file via the editor and Save
     <package>foo.com.model</package>
   <entity class="Employee"</entity>
Verify no errors appear and Employee can be resolved
... ... Update the following Entity in orm mapping file via the editor and Save
     <package>foo.com</package>
     <entity class="model.Employee"</entity>
Verify errors appear and employee cannot be resolved due to package name being split in EL orm mapping file at end of model in package
... ... Update the following Entity in orm mapping file via the editor and Save
     <package>foo.com.model.</package>
     <entity class="Employee"</entity>
Verify errors appear and employee cannot be resolved due to . at end of model in package
... ... Update the following Entity in orm mapping file via the editor and Save
     <entity class="foo.com.model.Employee"</entity>
Verify no errors appear and employee can be resolved
... ... Update the project from Generic to EclipseLink 2.3.x and Save Project is updated to EclipseLink project without error
... ... Remove Employee entity from the orm.xml mapping file and Save Employee enitity is removed successfully
... ... Create EclipseLink orm Mapping file and add the following Entity to the eclipsselink orm mapping file via the editor and Save
     <package>foo.com.model</package>
   <entity class="Employee"</entity>
Verify no errors appear and Employee can be resolved
... ... Update the following Entity in orm mapping file via the editor and Save
     <package>foo.com.model.</package>
     <entity class="Employee"</entity>
Verify no errors appear and employee can be resolved
... ... Update the following Entity in orm mapping file via the editor and Save
     <package>foo.com</package>
     <entity class="model.Employee"</entity>
Verify errors appear and employee cannot be resolved due to package name being split in EL orm mapping file at end of model in package
... ... Update the following Entity in orm mapping file via the editor and Save
     <entity class="foo.com.model.Employee"</entity>
Verify no errors appear and employee can be resolved
370779 Refactoring NPE moving an id class that is specified in java Create JPA project, Create the following JPA entity in model package
   package foo.com;
   @Entity
   @IdClass(EmployeeId.class)
   public class Employee {
   }
Project and entity are created successfully
... ... Create the following class in the same package
   package foo.com;
   public class EmployeeId {} 
Class is created successfully
... ... Add the orm mapping file to the project and add the following into the orm mapping file and Save
   <entity class="foo.com.Employee">
   <attributes>
       <id name="id">
       </id>
   </attributes>
  </entity>
Verify orm.xml is saved without error in error log
... ... Create a new package (model) in the project Package is created successfully
... ... R-click on EmployeeId Select Refactor>Move Move dialog appears
... ... Select the package to move EmployeeId to and Click on the Preview button Move dialog updates and shows the changes to be performed and no NPE appears in the Error log
... ... Click on the ok button Verify EmployeeId was moved to another package and if you hover over @IdClass(EmployeeId.class) in the Employee entity editor it shows model.EmployeeId
370877 missing java eclipselink customizer validation Create JPA (EclipseLink) project, Create the following JPA entity in model package
    package model;     
    @Entity
    @Customizer(FooCustomizer.class)
    public class Employee {}
Project and entity are created successfully
... ... Create the following class in a different package
    package com.foo;
    public class FooCustomizer {
       private FooCustomizer() {
           super();
       }
    }
Verify validation appears in problems pane stating The entity customizer class "com.foo.FooCustomizer" must have a public, zero-argument constructor.
371295 ClassCastException: GenericOrmVirtualAssociationOverride cannot be cast to OrmAssociationOverride2_0 Import the attached project into Dali Project is imported successfully
... ... R-Click on the project and select Properties Properties dialog appears
... ... Select JPA, Make sure EL 2.3 library is checked, Select Project Facets, Make sure Java 1.6 is selected, Click on Runtimes Tab and Make sure jdk 1.6 or newer is selected. Click on OK button for properties Properties dialog closes and project is updated successfully if necessary
... ... Open the Addr entity in the editor, change something and then Save the project Verify no ClassCast Exception appears in the Error log.
372340 cannot view project preferences JPA->Errors/Warnings page Create JPA Project JPA project is created successfully
... ... R-Click on the project and select Properties Properties dialog appears
... ... Select JPA>Errors/Warnings Verify the Errors/Warnings page appears without any errors
... ... Check the Enable project specific settings checkbox Verify all project specific settings expandable items on page become enabled
... ... Expand and collapse all project specific settings Verify all project specific settings can be expanded and collapsed without error

Back to the top