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.
Dali 3.1 M3
Dali 3.1 M3 Manual Testing
Steps to install 3.1 M3
- Dali 3.1 builds are found here: http://build.eclipse.org/webtools/committers/
- Download the Eclipse SDK (Indigo SR1) from the build page (or wherever)
- Unzip and run the Eclipse SDK, update proxy if necessary.
- Help-> Install New Software...
- Add a Software Site - append "/repository" to the build page URL for the Dali build you wish to use
- Make sure the Indigo software site is checked (should be by default) in "Available software sites"
- Select to install software from your newly added Dali site
- Select the SDK or non-SDK Dali depending on your needs (Category name needs to be update)
- Complete wizard and you are done. All the pre-reqs will be downloaded for you.
Bug No. | Description | Test Steps | Test Step Results |
310876 | cannot restore overwrite dialog for entity wizard | Create a JPA 2.0 project with DB connection | JPA Project is created successfully |
... | ... | R-Click on the Project, Select JPA Tools > Generate Entities from Tables, Add two tables to the JPA Project | Two Entities are created sucessfully |
... | ... | R-Click on the Project, Select JPA Tools > Generate entities from Tables, Select the same two tables and click 3 times and then click on Finish | Verify Overwrite Existing Class dialog appears |
... | ... | Check the Do not show this message again dialog and click on Yes To All button | Verify Entities are created/overwritten successfully |
... | ... | R-click on the Project, Select JPA Tools > Generate entities from Tables, Select the same two tables and click 3 times and then click on Finish | Verify Overwrite Existing Class dialog does not appear and Entities are created/overwritten successfully |
... | ... | Select Window>Preferences, Select Java Persistence | Verify Clear all 'do not show again' settings and show all hidden dialogs again. with a Clear button appear |
... | ... | Click on the clear button and then click on OK button | Preferences dialog closes |
... | ... | R-Click on the Project, Select JPA Tools > Generate entities from Tables, Select the same two tables and click 3 times and then click on Finish | Verify Overwrite Existing Class dialog appears |
313797 | More recent version of document warning does not appear until after a clean/validate | Create JPA 1.0 / Generic 1.0 project with orm.xml file | Project is created successfully |
... | ... | R-Click on the project and select properties | Properties dialog appears |
... | ... | Change JPA to version 2.0, change platform to Generic 2.0, select correct library and click on OK | Verify 2 info messages appear for orm.xml and persistence.xml |
321736 | Add disable preference for confirmation dialogs | Create a JAXB Project and add a .xsd schema file to the project | JAXB Project and .xsd file are created successfully |
... | ... | R-Click on the .xsd file within the JAXB Project and select Generate>JAXB Classes | New JAXB Classes from schema dialog appears |
... | ... | Enter a package name and click on Next twice and then Finish button | Verify Generating JAXB Classes dialog appears and Do not show this message again checkbox appears and is unchecked |
... | ... | Check the Do not show this message again and click on the Yes button | Verify classes are created |
... | ... | R-Click on the .xsd file within the JAXB Project and select Generate>JAXB Classes | New JAXB Classes from schema dialog appears |
... | ... | Enter a package name and click on Next twice and then Finish button | Verify Generating JAXB Classes dialog does not appear and classes are overwritten/created |
... | ... | Select Window>Preferences, Select Java Persistence, Click on Clear button and then OK button | Preferences dialog closes |
... | ... | R-Click on the .xsd file within the JAXB Project and select Generate>JAXB Classes | New JAXB Classes from schema dialog appears |
... | ... | Enter a package name and click on Next twice and then Finish button | Verify Generating JAXB Classes dialog appears and Do not show this message again checkbox appears and is unchecked |
... | ... | Click on the No button | Verify dialog closes and classes still exist |
... | ... | Create JPA Project, Create Two Entites with at least 2-3 fields in each entity | JPA Project and Entities are created successfully |
... | ... | R-Click on the Project and Select JPA Tools > Generate Tables from Entities | Generate Tables from Entities dialog appears |
... | ... | Click on Finish button | Generating Tables dialog appears and Do not show this message again checkbox appears |
... | ... | Check the Do not show this message again checkbox and click on Yes button | Verify tables created successfully |
... | ... | R-Click on the Project and Select JPA Tools > Generate Tables from Entities | Generate Tables from Entities dialog appears |
... | ... | Click on Finish button | Verify Generate Tables dialog does not appear and db table(s) are updated successfully |
... | ... | Select Window>Preferences, Select Java Persistence, Click on Clear button and then OK button | Preferences dialog closes |
... | ... | R-Click on the Project and Select JPA Tools > Generate Tables from Entities | Generate Tables from Entities dialog appears |
... | ... | Click on Finish button | Generating Tables dialog appears and Do not show this message again checkbox appears |
... | ... | Check the No button | Verify Tables are not overwritten |
327929 | Validation, defaults, and content assist support for JAXB 2.2 enum annotations | Create JAXB Project and employee.xsd file to the project | JAXB Project is created successfully |
... | ... | R-Click on the employee.xsd file and select Generate>JAXB Classes... | New JAXB Classes from schema dialog appears |
... | ... | Enter model for package name and click on next twice and then Finish button | Classes are generated from the xsd file |
... | ... | Open GenderType in editor | Verify @XmlType and @XmlEnum appear correctly in the class without error and per http://download.oracle.com/javase/6/docs/api/javax/xml/bind/annotation/XmlEnumValue.html example(s) |
335596 | NamedQuery support on MappedSuperclasses | Create JPA 1.0/Generic 1.0 Project with oracle DB connection | Project is created successfully |
... | ... | Create a JPA Entity with 2 fields and make one of them the key | JPA Entity is created successfully |
... | ... | Change the Entity to a Mapped Superclass via JPA Details pane | Verify Queries section appears for Mapped Superclass in JPA Details pane and you can add a named query |
... | ... | Change the project from JPA 1.0/Generic 1.0 to JPA 1.0/EL 1.0.x | Verify Queries section still appears for the Mapped Superclass in JPA Details pane |
... | ... | Change the project from JPA 1.0/EL 1.0.x to JPA 2.0/Generic 2.0 | Verify Queries section still appears for the Mapped Superclass in JPA Details pane and you can add/remove named query or native named query |
... | ... | Change the project from JPA 2.0/Generic 2.0 to JPA 2.0/EL 2.0.x | Verify Queries section still appears for the Mapped Superclass in JPA Details pane and you can add/remove named query or native named query |
... | ... | Change the project from JPA 2.0/EL 2.0.x to JPA 2.0/EL 2.3.x | Verify Queries section still appears for the Mapped Superclass in JPA Details pane and you can add/remove named query or native named query |
348283 | Entity Gen Wizard: Should only provide the list of selected tables to Table 2 field | Create JPA project, with a db connection | Project is created successfully |
... | ... | R-Click on the project, select JPA Tools>Generate Entities from Table... | Generate Custom Entities dialog appears |
... | ... | Select 3 tables and click on the next button, Click on New Association button (+) | Create New Association dialog appears |
... | ... | Click on Table Selection button for Table 2 | Table Selection dialog appears and verify only the 3 selected tables appear in the list |
349015 | New JPA entity with IdClass, referenced incorrectly in orm.xml | Create JPA project | Project is created successfully |
... | ... | Create JPA entity, Select to add the entity to the orm.xml, Add 4 fields and check the key checkbox for at least two of the fields. | Entity is created successfully and verify no validation error "ID class does not exist on the project classpath" appears |
... | ... | Open the orm.xml in the editor | Verify the attributes you selected for the key both appear |
349316 | 'delimited identifiers' check box appearing for 1.0 orm.xml file | Create JPA 2.0 EL 2.3 project | Project is created successfully |
... | ... | Add orm.xml and eclipselink-orm.xml file(s) to the project | orm.xml and eclipselink-orm.xml file are created successfully for the project |
... | ... | Select orm.xml in JPA structure and expand Persistence Unit Section in JPA Details pane | Verify Delimited identifiers checkbox exists |
... | ... | In the editor for orm.xml, change entity-mapping version from 2.0 to 1.0 and orm_2_0.xsd to orm_1_0.xsd and save | Verify Delimited identifiers checkbox no longer exists in JPA Details pane |
... | ... | Select eclipselink-orm.xml in JPA structure and expand Persistence Unit section in JPA Details pane | Verify Delimited identifiers checkbox exists |
... | ... | In the editor for eclipselink-orm.xml, change entity-mapping version from 2.0 to 1.0 and orm_2_0.xsd to orm_1_0.xsd and save | Verify Delimited identifiers checkbox no longer exists in JPA Details pane |
357975 | Invalid JPQL error if named-query is in orm.xml | Create JPA project, Create entity (Foo) for the project with one field that is the primary key | Project and entity are created successfully |
... | ... | Select the Entity in the JPA Structure, Expand Queries section in JPA Details and click on Add | Add Query dialog appears |
... | ... | Enter select for the Name and select Named Query from the Type drop down and click on OK button | select appears in list for queries |
... | ... | Enter SELECT x FROM Foo x in the Query text field and Save the project | Verify the following annotation appears in the editor for the entity @NamedQuery(name = "select", query = "SELECT x FROM Foo x") |
... | ... | Add the JPA ORM Mapping File to the project, R-click on the Entity Mappings in the JPA Structure pane for the orm.xml mapping file and Add the Entity to the orm.xml file | Verify the Entity is added successfully to the orm.xml file |
... | ... | Add the following to the source for the orm.xml
<named-query name="select"> <query>SELECT x FROM Foo x</query> </named-query> |
Verify the error 'The abstract schema type 'Foo' is unknown' does not appear in the problems pane |
... | ... | Go to the persistence.xml and remove the entity (Foo) from the managed classes in persistence.xml and Save | Verify the error 'The abstract schema type 'Foo' is unknown' still does not appear in problems pane. |
358106 | JPQL completion proposal exception | Create JPA project and JPA Entity with 2 fields and make one a key field | JPA Project and Entity are created successfully |
... | ... | Add the following after @Entity in the editor @NamedQuery(name="asdf") and Save | Two errors appear one for query statement required and one for defining the query attribute |
... | ... | Place the cursor in from the @NamedQuery and being typing @NamedQueries then use Control->Space to complete the query | Verify the query completes without index out of bounds error |
359690 | [EclipseLink] converter validation too strict if converters are named the same but not in conflict | Create JPA2.0, EclipseLink 2.3.x project | Project is created successfully |
... | ... | Create two Entities with two fields (1 being the key) for each | Entities are created successfully |
... | ... | Select an Entity, In JPA Details pane expand Converters and add a custom converter and name it TestConverter and select a Class | Converter is created successfully |
... | ... | Select the other Entity, In JPA Details pane expand Converters and add a custom converter and name it TestConverter (do not select a class at this time). Save all. | Verify no duplicate errors appear since they have different types |
360002 | NPE error when you add a JPA annotation to a class constructor | Import the attached JPA project (this is attached to the bug) into your workspace | Project is imported successfully |
... | ... | R-Click on the project and add the correct libraries and save the project | Project is saved library errors are corrected |
... | ... | Open the PropertyRecord class in the editor, goto the @ElementCollection annotation, hit return, Enter @CollectionTable hit the space key, hit Ctrl-Space for content assist | Verify content assist shows list of avaliable items |
... | ... | Double click on PropertyRecord | Verify no NPE error appear and the PropertyRecord is added to the editor |
362064 | NPE changing access type to PROPERTY in orm.xml without property methods | Import the attached project from bug 362064 into your workspace | Project is imported successfully |
... | ... | Open the eclipselink-orm.xml from the imported project | eclipselink-orm.xml appears in the editor |
... | ... | In the JPA Details pane, select Property from the Access drop down in the Entity Mappings section | Verify <access>PROPERTY</access> appears in the source for the eclipselink-orm.xml and no errors appear |
362225 | JoinTable specified inverse join columns invalid validation | Import the project attached to bug 362225 into your workspace | Project is imported successfully but with errors |
... | ... | R-Click on the project, Select Properties, Add the EL library and Click on OK | Errors are removed |
... | ... | Open the EntityA.java entity, Select bs field in the JPA Structure pane | Verify in the JPA Details pane the Inverse Join columns has Override default checkbox checked and ENTITYB_ID -> ID appears |
362598 | generated canonical metamodel classes all have validation warning | Create JPA 2.0, EL2.3 project | Project was created successfully |
... | ... | Create 2 Entities with at least 2 fields with one of them in each being the Key | Entities created successfully |
... | ... | R-click on the project, Select Properties, Highlight JPA, select src from the Canonical metamodel drop down box and then click on the OK button | Verify the canonical metamodels were created (2 since there were 2 entities) successfully and no warnings appear stating - Class "XXX_" is annotated, but is not included in any persistence unit |