Dali 3.1 M1

From Eclipsepedia

Jump to: navigation, search

Dali 3.1

Dali 3.1 M1 Manual Testing

Manual Testing for 3.1 M1 Release
Bug No. Description Test Steps Test Step Results
195832 [Entity Gen] Add option to refresh DB metadata prior to entity generation Create a JPA 2.0, Generic 2.0 project with an Oracle 11 db Project is created successfully
... ... R-Click on the Project and select JPA Tools > Generate Entities from Tables... Generate Custom Entites dialog appears and lists the tables in the Oracle DB
... ... Use Toplink to drop add a table to the DB Verify the table does not appear in the list.
... ... Click on the Refresh button Verify the newly added table appears in the list
... ... Disconnect from the db and then connect to the db and remove the clear the tables http://ottvm065.ca.oracle.com:7001/QALabWebsite/ DB tables are cleared
... ... Connect to the Oracle DB, R-Click on the Project and select JPA Tools > Generate Entities from Tables... Generate Custom Entites dialog appear but no tables appear since DB was cleared
... ... Use TopLink again and add the Employee Tables back to the db, then click on the Refresh button Verify the tables appear in the list
311945 Remove unset*JoiningStrategy API from RelationshipReferences
348639 ClassCastException: SourceField/SourceMethod cannot be cast to JavaResourceAbstractType
339562 Warning for the extra persistence-unit-metadata does not show up in the sources Create JPA 2.0, Generic 2.0 project Project is created successfully
... ... Create an entity Entity is created successfully
... ... R-Click on the project and select New > JPA ORM Mapping File New mapping file dialog appears
... ... Leave the defaults and click on Finish orm.xml file is created and opened in editor
... ... In the JPA Details pane expand Persistence Unit and check the XML Mapping metadata complete checkbox persistence-unit-metadata element information appears in the source of the orm.xml editor
... ... R-Click on the project and select New >JPA ORM Mapping File New mapping file dialog appears
... ... Change the name to orm2.xml and click on the finish button orm2.xml file is created and opened in editor
... ... In the JPA Details pane expand Persistence Unit and check the XML Mapping metadata complete checkbox and then Save the project Verify two warnings appear stating Extraneous persistence unit metadata found cross the persistence unit. This metadata may not be used.
... ... Double click on the first warning in the problems pane Verify you are taken to the orm.xml editor source pane
... ... Double click on the second warning in the problems pane Verify you are taken to the orm2.xml editor source pane
342999 Binding file selection not consistent with Schema file selection Create JAXB Project, Add a Class and Create a Schema Project, class and Schema are created successfully
... ... R-Click on the JAXB Project and select New > Other New Dialog appears
... ... Select JAXB > JAXB Classes from Schema and click on Next, Select the JAXB project and click on Next, Select the schema xsd file and click on Next button Generate Classes from Schema: Name of selected schema.xsd page appears
... ... Click on Add button for Bindings files Verify External Bindings File Selection dialog appears with a list of Workspace files listed and verify the created JAXB Project exisits in the list
348639 ClassCastException: SourceField/SourceMethod cannot be cast to JavaResourceAbstractType Create JAXB Project JAXB Project is created successfully
... ... R-Click on JAXB Project and select New > Class New Java Class dialog appears
... ... Enter a package name (ex. model) and Name (ex. Foo)and click on Finish Class is created successfully without error
... ... Add the following to the class and Save
       private Integer Address_ID; 
 	 private String City;

public Integer getAddress_ID() {

		return this.Address_ID;

}

public String getCity() {

		return this.City;

}

Class is updated and no errors appear
... ... Add the following to the Class before public class Foo
  import javax.xml.bind.annotation.XmlType;
  @XmlType
Verify no errors appear in problems pane or Error Log
... ... Enter @XmlType prior the the first field and Save Verify no errors appear in error log but 2 errors appear in Problems pane
... ... Remove @XmlType from before the first field to be in the middle of the two fields and Save Verify the errors in the problems pane remain the same and no errros appear in Error log
348773 [Validation] Validation for duplicate entity names and mapping file mapped classes Create a new JPA 2.0, EL 2.1.x, project Project created successfully
... ... Create 3 entities within the same package Entities are created successfully
... ... R-Click on the project and select New>JPA orm mapping file orm.xml file created and opened in editor
... ... R-Click on the Entity Mappings in the JPA Structure tab for the orm.xml, Select Add Class, Select an entity you created and click on OK Entity is added without any error/warnings
... ... R-click on the Entity Mappings in the JPA Structure tab for the orm.xm., Select Add Class, Select the same entity that you previously selected Verify warning appears in the Add Class dialog stating - File already contains that persistent class
... ... Click on the OK button. Save the project Verify 2 errors and 2 warnings appear stating - Duplicate class "name" found in mapping files. This configuration is not supported by the tooling and may result in invalid error messages. Duplicate entity name "name" found in the persistence unit. Entity names must be unique.
... ... Remove the duplicate class from the orm.xml file and Save the project Verify the error(s) and warning(s) are removed.
... ... Create a new Entity with the same name but in a different package New entity is created with the same name as in the other package
... ... Go back to orm.xml and add the new entity to the orm.xml that has the same name as the one already in there, but with the different package Verify the following error appears - Duplicate entity name "name" found in the persistence unit. Entity names must be unique.
... ... Change the type of one of the same named entities from entity to embeddable, Save the project Verify the error is removed since the Types are different.
349218 [EclipseLink] Customizer validation appearing on entity in orm.xml Create JPA 2.0, EL 2.2.x project Project is created successfully
... ... Create an entity with one or two fields Entity is created successfully
... ... R-click on the project select New > Eclipselink ORM Mapping File eclipselink-orm.xml mapping file is created and opened in editor
... ... R-click on the Entity Mapping in JPA Structure pane and select Add Class Add Class dialog appears
... ... Add the created Entity and click on OK, Expand the Advanced section in JPA Details pane, Enter a space in the customizer Class Text field Verify the following text appears in the source for eclipselink-orm.xml <customizer class=" "/>
... ... Save the project Verify the error appears on the <customizer class=" "/> and the following error appears in the Problems pane 'An entity customizer class should be specified'
... ... Change the " " to "f" in the eclipselink-orm.xml source Verify the error still appears on the <customizer class="f"/> and the following error appears in the Problems pane 'The entity customizer class "f" does not exist on the project classpath'
... ... Change the "f" to "java.lang.String" in the eclipselink-orm.xml source Verify the error still appears on the <customizer class="f"/> and the following error appears in the Problems pane 'The entity customizer class "java.lang.String" does not implement the org.eclipse.persistence.config.DescriptorCustomizer interface'
349330 unnecessary 'duplicate generator' validation when name is "" Create JPA 2.0, EL 2.2.x project Project is created successfully
... ... Create Class, and just enter MyConverter for the name and finish Class is created without error
... ... Create JPA Entity, with one field for id JPA Entity is created successfully and appears in editor
... ... Add the following to the Entity in the editor @TableGenerator(name="")

@SequenceGenerator(name="") @Converter(name="", converterClass=MyConverter.class) @TypeConverter(name="")

Verify the following 2 errors do not appear in the problems pane - Duplicate Generator named "" defined in this persistence unit
351975 NPE entering special characters to customizer class combo Create JPA 2.0, EL 2.2.x project Project is created successfully
... ... Create 2 JPA entities with 2 or 3 fields and one being an Id field JPA Entity is create successfully
... ... Select the Entity in JPA Structure Pane, Expand Advanced Section in JPA Details pane Advanced section expands
... ... Enter period(.), comma(,) or another special character into the Customizer Class field and Save project Verify NPE does not appear in error log, veify @Customizer appears in editor and error appears in problems pane stating The annotation @Customizer must define the attribute value. <None> appears in the Customizer Class field in JPA Details pane
... ... Click on Browse for Customizer Class, Select the other JPA entity and click on OK Verify the package.entity appears for Customizer Class and error is removed from problem pane
353883 [EclipseLink] Add 1-m, m-m, 1-1, element-collection, m-1 to xml and noncacheable element is added Create JPA 2.0, EL 2.1.x project Project is created successfully
... ... Create 2 JPA Entities with 2 or 3 fields each Entities are created successfully
... ... R-click on the project and select New > EclipseLink ORM Mapping file eclipselink-orm.xml file is created
... ... Add an Entity to the eclipselink-orm.xml mapping file Entity is added to mapping file
... ... R-Click on a field in the Entity of the JPA Structure pane and select Add Attribute to XML and Map... Add Attribute dialog appears
... ... Select One to One from the Map as drop down and click on OK Verify the source for eclipselink-orm.xml shows the following - <one-to-one name="attr"> </one to one>