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 "Dali 3.2 M5"

Line 404: Line 404:
 
| Select JAXB, select EL 2.3 for the library, Select Project Facets, Update Java to 1.7, Update runtime to  jdk 1.7 and then click on OK button.
 
| Select JAXB, select EL 2.3 for the library, Select Project Facets, Update Java to 1.7, Update runtime to  jdk 1.7 and then click on OK button.
 
| Verify no errors appear for the project
 
| Verify no errors appear for the project
 +
|-
 +
| 368554
 +
| Entity Gen: Update persistence.xml default has changed to false
 +
| Create JPA project with DB connection
 +
| Project is created successfully
 +
|-
 +
| ...
 +
| ...
 +
| R-click on the project and select JPA Tools > Generate Entities from Tables...
 +
| Generate Custom Entities dialog appears and verify Update class list in persistence.xml checkbox is checked by default.

Revision as of 14:48, 30 January 2012

Dali 3.2

Dali 3.2 M5 Release Manual Testing

Manual Testing for 3.2 M5 Release
Bug No. Description Test Steps Test Step Results
307186 EclipseLink Converter panel is enabled on virtual orm attribute mapping Create JPA (EclipseLink) project, Create JPA entity with at least 2 fields one of which is an ID field. Project and entity are created successfully
... ... In the Entity add the following after @ID annotation and Save - 
   @Convert("a")
   @ObjectTypeConverter(
   dataType = FooConverter.class, 
   objectType = FooConverter.class, 
   name = "a", 
   conversionValues = @ConversionValue
   dataValue = "aa", objectValue = "bb"))
Verify JPA Details is updated
... ... Add EclipseLink ORM Mapping file to the project EclipseLink ORM mapping file is added successfully
... ... Add the Entity to the EL orm Mapping file and Save, Then select the Id field, and in the JPA Details pane expand the Converters field Verify the Converters field are disabled in the JPA Details pane for the ID field in the Entity
331960 plural converter annotations added in EclipseLink Create JPA EL 2.1 project with DB connection, Create some entities from tables, Open an entity in the editor, Type @Conv in editor for an attribute and then hit ctrl-space Verify Converters does not appear
... ... Create JPA EL 2.2 project with DB connection, Create some entities from tables, Open an entity in the editor, Type @Conv in editor for an attribute and then hit ctrl+space Verify Converters appears in the list
... ... Remove @Conv and enter @Object then hit ctrl+space Verify ObjectTypeConverter and ObjectTypeConverters appears in list
... ... Remove @Object and enter @TypeCon then hit ctrl+space Verify TypeConverter and TypeConverters appears in list
... ... Remove @TypeCon and enter @StructC then hit enter Verify StructConverter and StructConverters appear in list
... ... Create JPA Project connected to Oracle DB with some tables that have plurel names (Ex. Respons) Project is created successfully
... ... R-click on Project, Select JPA Tools>Generate Entities from Tables.. Generate Custom Entities dialog appears
... ... Select 1 or 2 tables that have a plurel name (ex. Respons), Finish and Save project Verify the entities created have a class name that is plurel and is not cutting off the 's'
348279 Entity Gen Wizard: Better to show a default schema when choosing a connection Create a DB connection but do not connect to the DB yet DB connection is created successfully
... ...
350615 [EclipseLink] Point to latest XSD's in shipped EL bundles in XML Catalog Download latest Dali build and go to Plug-in's directory and open org.eclipse.jpt.common.eclipselink.core jar file Verify plugin.xml file exists
... ... Open plugin.xml file Verify eclipselink_oxm_2_4.xsd file is pointing to the platform plugin
... ... Close plugin.xml file, Go back to plugins directory, open org.eclipse.persistence.jpa jar file Verify eclipselink_orm_2_4.xsd file exists
361866 [EclipseLink] add primary-key checkbox to tenant-discriminator-column UI for EL 2.4 Create JPA EclipseLink 2.3 project with DB connection JPA project is created successfully
... ... Generate two entites from tables from the DB Entities are created successfully
... ... Select an entity and view it in JPA Details pane, Expand the Multitenancy section, Check the override default checkbox, Select an item in the list box Verify that Primary key checkbox does not appear
... ... Create JPA EclipseLink 2.4 project with DB connection JPA project is created successfully
... ... Generate two entites from tables from the DB Entities are created successfully
... ... Select an entity and view it in JPA Details pane, Expand the Multitenancy section, Check the Multitenant Stratgey checkbox, Check the override default checkbox, Select an item in the list box, Select name from the drop down list. Verify that Primary key checkbox appears
... ... Change the attribute mapping for the primary key attribute mapping to be mapped as basic. Verify the following error appears in the problems pane 'The entity has no primary key defined'
... ... Check the Primary Key checkbox and save the project Verify editor is updated to show primaryKey = true and the error is removed from the problems pane
... ... Repeat the above steps for eclipselink orm mapping file Verify the same results
364071 [EclipseLink] add Structure and Array attribute mapping support Create JPA EL 2.2 project and create JPA entity with 2 fields Verify the field cannot be mapped as Array or Structure mapping
... ... Create JPA EL 2.3 project with DB connection JPA project is created successfully
... ... R-Click on JPA project, select JPA Tools > Generate Entities from Tables... Generate Custom Entities
... ... Select one or two tables (ex. Address, Employee) and generate entities Entities are generated successfully
... ... Open Entity in editor, Select a field within the entity JPA Structure, Click on the mapping link in JPA Details to change mapping type Mapping Type Selection Dialog appears and verify Array and Structure appear in the list of mappings
... ... Select Structure and click on OK Verify mapping is updated to Structure and no errors appear
... ... R-click on project, Select properties Properties dialog appears
... ... Select JPA, Select src from the source folder drop down for Canonical metamodel and then click on OK button to close Properties Verify the field that you changed to a structure type appears in the canonical metamodel that was created
... ... R-Click on project, Select New>EclipseLink ORM Mapping file New EclipseLink Mapping file dialog appears
... ... Leave defaults and click Finish button EclipseLink orm mapping file is created successfully
... ... Add the Entity to the mapping file, R-click on the structure mapping type field, Select Add Attribute to XML and Save Verify mapping file source was updated with <structure name="fName"> and no errors appear
... ... In the source for eclipselink-orm hit enter after <structure name="fName"> and enter < Verify the only items available are access-methods and property
... ... Remove <, return to entity editor, Select another attribute in JPA Structure and click on Basic mapping link in JPA Details Mapping Type Selection dialog appears
... ... Select Array and click on OK, Save project Verify the following error appears in problems pane 'The annotation @Array must define the attribute database Type
... ... Enter (databaseType="varchar") after @Array in editor and Save project Verify error is removed from problems pane
... ... Add this attribute to the eclipselink-orm mapping file and save. Verify the following error appears in problems pane 'cvc-complex-type.4: Attribute 'database-type' must appear on element 'array'.
... ... Enter database-type="varchar"> after <array name='Name' in eclipselink-orm editor and Save project Verify error is removed from the problems pane
... ... Hit Enter after <array name="lName" database-type="varchar"> and enter < Verify a list of supported items contains support for a column, lob, enumerated, temporal, and eclipselink convert and converters
... ... Enter <column = "L_NAME"/> and Save project Verify the following error appears stating Element type "column" must be followed by either attribute specification, ">" or "/>"
... ... Enter the correct syntax for the column (Ex. <column name="L_NAME"/> ) and Save project Verify error is removed
... ... Enter <lob/> and Save Verify no errors appear
... ... Select an attribute from the entity in the mapping file that is a date type, R-click, Select Add Attribute to XML and Map... Add Attribute dialog appears
... ... Select Array from the Map As drop down and click on OK Attribute is added to mapping file
... ... Add the databate-type to the Array in the editor, Add <temporal>DATE<temporal/> and Save Verify no errors appear
... ... Remove <temporal>DATE<temporal/> and enter <enum and hit ctrl+space Verify <>enumerated appears for content assist
... ... Select <>enumerated and then save Verify <enumerated><enumaterated/> appears in mapping file editor, Verify two errors appear for enumerated values not being valid
... ... Enter STRING or ORDINAL for the enumerated value (ex. <enumerated>STRING<enumerated/> ) and Save project Verify errors are removed
... ... Go back to the entity editor, select an attribute, change mapping to Array and Save Verify @Array appears in editor, Verify error appears stating 'The annotation @Array must define the attribute databaseType
... ... Add the following after @Array in editor (databaseType="varchar") and Save Verify error is removed
... ... Add the following annotation below @Array annotation @Convert("test") and Save Verify the following error appears stating - 'The specified converter "test" for mapping "fname" cannot be resolved'
... ... Add the following annotation below @Convert annotation @TypeConverter(name="test") and Save Verify error is removed
... ... Repeat all the steps for EclipseLink 2.4 project Verify all results pass
364206 "REFRESH" ON "GENERATE ENTITIES" WIZARD RESULTS NPE WHEN DB IS NOT CONNECTED Setup some DB connections but do not connect to the DB at this time. Create a JPA project with DB connection but do not connect to DB at this time JPA Project is created successfully
... ... R-click on the project, Select JPA Tools > Generate Entities from Tables... Generate Custom Entities dialog appears. Verify the Refresh Tables button, Select All button and Disable All button are disabled since the DB is not connected and you cannot click on them.
... ... Click on the Connect button Verify the DB is connected and the buttons become enabled
365488 JPA perspective 'New Entity' tool bar button is not a drop-down with e4 platform Launch Eclipse, Select Window>Open Perspective>Other Open Perspective dialog appears
... ... Select JPA and click on OK button JPA perspective appears
... ... Click on New Entity drop down button Verify the following items appear - JPA Entity, JPA ORM Mapping File, EclipseLink ORM Mapping File
367325 [EclipseLink] Multitenant include-criteria support Create JPA EclipseLink 2.4 project with DB connection JPA project is created successfully
... ... Generate two entites from tables from the DB Entities are created successfully
... ... Select an entity and view it in JPA Details pane, Expand the Multitenancy section Verify that Include criteria (True) checkbox appears and is defaulted to True
... ... Check the checkbox Verify Include critera appears checked and (True) is removed since by checking it, it becomes true. Verify (includeCriteria = true) appears in the editor
... ... Uncheck the checkbox Verify Include criteria checkbox is unchecked. Verify (includeCriteria = false) appears in the editor
... ... Uncheck the Multitenant strategy checkbox Verify Include criteria (true) shows as a default and checkbox is grayed and checked
... ... Check the Multitenant strategy checkbox and select VPD from the drop down Verify Include criteria (false) shows as a default now and the checkbox is grayed and checked. Verify @Multitenant(value = VPD)
... ... Check the Include criteria checkbox Verify Include criteria shows without (false) in JPA Details. Verify (includeCriteria = True) appears in the editor
... ... Uncheck the Include criteria checkbox Verify editor is updated with (includeCriteria = false)
... ... Click on the checkbox one more time Verify it is removed from the editor. Verify Include criteria (false) appears in the editor and the checkbox is grayed since this is the default.
... ... Repeat the steps for eclipselink orm mapping file Verify the results are the same
367890 [Validation] Improper validation for XmlElement with type specified alongside XmlJavaTypeAdapter Import the project that is attached to this bug Project is imported correclty
... ... R_Click on the project and select Properties Properties dialog appears
... ... Select JAXB, select EL 2.3 for the library, Select Project Facets, Update Java to 1.7, Update runtime to jdk 1.7 and then click on OK button. Verify no errors appear for the project
368554 Entity Gen: Update persistence.xml default has changed to false Create JPA project with DB connection Project is created successfully
... ... R-click on the project and select JPA Tools > Generate Entities from Tables... Generate Custom Entities dialog appears and verify Update class list in persistence.xml checkbox is checked by default.
Retrieved from "https://wiki.eclipse.org/index.php?title=Dali_3.2_M5&oldid=287461"

Back to the top