Dali 3.2 M6

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
331480	[Validation] Need validation for embeddable id class	Create JPA EclipsLink 2.4.x project	Project is created successfully
...	...	Create the following class package model; @Embeddable public class Id {}	Class is created successfully and contains on error in problems pane
...	...	Create the following entity package model; @Entity public class Foo { @EmbeddedId private Id Test_Id; }	Entity is created and verify the following 2 errors appear in problems pane Embedded ID class should impletment java.io.Serializable Embedded ID class should include method definitions for equals() and hashcode()
...	...	Change public class Id in Id.java editor to private class Id and Save	Verify the following error 2 appears Embedded ID class should be public Illegal modifier for the class Id; only public, abstract & final are permitted
...	...	Change private class Id back to public class Id, Remove @Embeddable from Id.java and Save	Verify the following error appears model.Id is not mapped as embeddable
351497	JPA Entities from Tables shouldn't allow default packages	Select Windows>Preferences	Preferences dialog appears
...	...	Select Java Persistence>JPA	Verify Entity generation from tables Default package shows model
...	...	Cancel out of Properties, Create New JPA project, R-Click on JPA Project and select JPA Tools>Generate Entities from Tables	Generate Custom Entities dialog appears
...	...	Select two tables and click on next button twice,	Verify Customize Defaults page appears and model appears in package field
...	...	Click on the Finish button	Verify entities are generated in the model package
...	...	Select Window>Preferences, Java Persistence>JPA and change the default package from model to foo.model.test and click on OK button. Create New JPA project, R-Click on JPA Project and select JPA Tools>Generate Entities from Tables	Generate Custom Entities dialog appears
...	...	Select two tables and click on next button twice,	Verify Customize Defaults page appears and foo.model.test appears in package field
...	...	Change foo.model.test to test.model.foo and click on Finish button	Verify entities are generated in the test.model.foo package
358258	4.2 platform- selection from JPA structure to java editor does not work	Create JPA Project, Create JPA Entities with a few attributes	Project and entities are created successfully
...	...	In JPA structure select an attribute for the Entity you created	Verify the attribute you selected in the JPA Structure is the focus in the Editor
...	...	Select different attributes in both the JPA Editor and JPA Structure for the Entity	Verify the JPA Structure and JPA Editor are both updated accordingly
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(com.foo.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. The entity customizer class "com.foo.FooCustomizer" does not implement the org.eclipse.config.DescriptorCustomizer interface.
370895	Static weaving results in infinite builder loop when enabled	Create a JPA EclipseLink Project with DB connection	JPA Project is created successfully
...	...	R-Click on project and select Properties	Properties for the project dialog appears
...	...	Select JPA>EclpseLink	EclipseLink Configure the EclipseLink preferences for the project page appear and the Weave classes on build checkbox is disabled by default
...	...	Check the Weave classes on build checkbox	Verify the 4 fields become enabled
...	...	Click on the OK button	Verify the Console tab becomes the focus and it shows it picked up JAVA_TOOL_OPTIONS and _JAVA_OPTIONS and no errors appear in the console. Verify that in the Console there is no text being spit out every few seconds. Also look at the job status indicator at the bottom right of the screen and verify it does not continue running in a loop without activity in the project.
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
372876	Dynamic Entity Generation from Tables	Create JPA EclipseLink 2.4.x project with an Oracle DB connection	Project is created successfully
...	...	R-click on the project, select JPA Tools > Generate Dynamic Entities From Tables...	Generate Dynamic Ectities dialog appears
...	...	Select two or three tables and click on next button	Table Associations page appears
...	...	Add a one to one table association and click on Next button	Customize Defaults page appears
...	...	Click on the Next button	Customize Individual Entities page appears
...	...	Click on Finish button	Verify eclipselink-orm.xml appears in editor and JPA Structure pane with the selected Dynamic Entities
373150	[EclipseLink] JPA Structure 'Add Virtual Attribute' action	Create JPA EclipseLink project, JPA Entity with 2 or 3 attributes and EclipseLink ORM Mapping file	Project, Entity and mapping file are all created successfully
...	...	Open EclipseLink ORM mapping file, R-click on it in JPA Structure pane and Add the entity to the mapping file	Entity is added successfully to the EL Mapping file
...	...	R-click on the Entity in the EL Mapping File in the JPA Structure pane	Verify Add Virtual Attribute... now appears for selection
...	...	Click on Add Virtual Attribute...	Verify Add Virtual Attribute dialog appears with Name field, Map As drop down, Attribute type field with Browse button
...	...	Enter Name (Province) and select Basic from Map As drop down	Verify OK button is disabled and message states 'You must specify an attribute type'
...	...	Enter java.lang.String for attribute type and click on OK button	Verify Virtual Attribute appears in the Entity in EL Mapping file without errors.
...	...	R-click on the Entity in JPA Structure pane and select Map As > Mapped Superclass	Virtual Attribute is removed and Entity is updated to Mapped Superclass
...	...	R-Click on the Mapped Superclass	Verify Add Virtual Attribute... appears for selection
...	...	Click on Add Virtual Attribute...	Verify Add Virtual Attribute dialog appears with Name field, Map As drop down, & Attribute type field and Browse button appear
...	...	Enter Name (Province), select Basic from Map As drop down, Enter java.lang.String for the Attribute type and click on OK button	Verify Virtual Attribute appears in the Mapped superclass in EL Mapping file
...	...	R-Click on Mapped Superclass in JPA Structure pane and select Map As > Embeddable	Virtual Attribute is removed and Mapped Superclass is updated to Embeddable
...	...	R-Click on Embeddable	Verify Add Virtual Attribute... appears for selection
...	...	Click on Add Virtual Attribute...	Verify Add Virtual Attribute dialog appears with Name field, Map As drop down, & Attribute type field and Browse button appear
...	...	Enter Name (Province) select Basic from Map As drop down, Enter java.lang.String for the Attribute type and click on OK button	Verify Virtual Attribute appears in the Embeddable in EL Mapping file
...	...	Create JPA EL 2.4 project, Generate Dynamic Entities from Tables, use 1 or 2 tables and generate	Eclipselink orm mapping file is generated and contains the dynamic entities
...	...	R-Click on the Entity Mappings in the JPA Structure pane for the EclipseLink orm mapping file and select Add Virtual Attribute	Verify Add Virtual Attribute dialog appears with Name, Map As & Attribute type fields.
...	...	Enter Name (Testing) select Basic from Map As drop down, Enter java.lang.String for the Attribute type and click on OK button	Verify Virtual Attribute appears in the EL Mapping file
373414	[EclipseLink] support DDL generation for dynamic classes using the DynamicClassLoader	Create JPA EclipseLink 2.4.x Project with Database connection	Project is created successfully
...	...	R-click on Project and select JPA Tools > Generate Dynamic Entities from Tables	Generate Dynamic Entities dialog appears
...	...	Select 3 tables and then click Finish button	EclipseLink-orm mapping file appears containing the 3 dynamic entities
...	...	R-Click on the project and select JPA Tools > Generate Tables from Entities	Generate Tables from entities dialog appears
...	...	Select Both radio button and click on the Finish button	Verify the tables are dropped and created on the DB and the createDDL.sql and dropDDL.sql files are added to the project.