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.
Difference between revisions of "Dali 3.3 M7 Release"
Line 17: | Line 17: | ||
| Create a JPA Entity with an attribute that is set as the primary key but is not the same name as a name in the database so it will not be resolved | | Create a JPA Entity with an attribute that is set as the primary key but is not the same name as a name in the database so it will not be resolved | ||
| Verify JPA entity is created and only 1 error appears in problems pane stating Column "id" cannot be resolved on table "TableName" | | Verify JPA entity is created and only 1 error appears in problems pane stating Column "id" cannot be resolved on table "TableName" | ||
+ | |- | ||
+ | | 391578 | ||
+ | | EclipseLink OXM Mapping File creation wizard | ||
+ | | Create JAXB Project | ||
+ | | JAXB project is created successfully | ||
+ | |- | ||
+ | | ... | ||
+ | | ... | ||
+ | | | ||
+ | | | ||
|- | |- | ||
| ... | | ... |
Revision as of 10:59, 8 May 2013
Dali 3.3 M7 Release Manual Testing
Bug No. | Description | Test Steps | Test Step Results |
380021 | Extra invalid validation error against default primary key join column of entity | Create a JPA project | JPA Project is created successfully |
... | ... | Create a JPA Entity with an attribute that is set as the primary key but is not the same name as a name in the database so it will not be resolved | Verify JPA entity is created and only 1 error appears in problems pane stating Column "id" cannot be resolved on table "TableName" |
391578 | EclipseLink OXM Mapping File creation wizard | Create JAXB Project | JAXB project is created successfully |
... | ... | ||
... | ... | Select a Name from the column name drop down and Save the project | Verify the error in the problem pane disappears |
392222 | Remove "Create mapping file (orm.xml)" option from new project wizard | Select File > New > JPA Project | New JPA Project dialog appears |
... | ... | Enter a name and click on next button twice | JPA Facet page appears and verify Create Mapping File (orm.xml) checkbox does not appear for selection. |
397391 | NPE: 1-m/m-m switch joining strategy from JoinTable to JoinColumns or MappedBy | Create JPA Project and JPA Entities with at least 2 or more attributes | Project and entities with attarbutes are created successfully |
... | ... | Select an attribute from an entity in the JPA Structure pane and then change the mapping to One-To-Many and expand Joining Stratagy in JPA Details pane | Verify attribute is mapped as One-To-Many, Verify Joining Stratagy has Join Table radio button selected as default |
... | ... | Click on Join Columns radio button | Verify no NPE error appears in the Error Log |
... | ... | Click back on Join Table radio button | Verify no errors appear in the Error log |
... | ... | Click on Mapped By radio button | Verify JPA Details is updated and no errors appear in the Error Log |
... | ... | Change the mapping from Ont-To-Many to Many-To-Many | Verify mapping is changed successfully with no errors in Error Log |
... | ... | Expand Joining Stratagy in JPA Details pane | Verify Join Table is selected by default |
... | ... | Select Mapped By radio button | Verify JPA Details is updated and no errors appear in Error Log |
... | ... | Select Join Table radio button | Verify JPA Details is updated and no errors appear in Error Log |
404673 | Confusion exists with EclipseLink 2.4.x/2.5.x platform and EclipseLink 2.5 mapping file | Create a JPA 2.0 project with EclipseLink 2.4.x/2.5.x platform and EclipseLink 2.5.0 library | Project is created successfully without error |
... | ... | R-click on the project and select New > EclipseLink ORM Mapping File | New EclipseLink Mapping File dialog appears |
... | ... | Click on the finish button | Verify eclipselink-orm.xml is created successfully and opened in the editor and the version shows 2.4 on the Details tab (even though you selected EL 2.5 library it will default to 2.4 for JPA 2.0) and no errors appear in Problems tab |
... | ... | Change version in Details tab from 2.4 to 2.5 and in source tab from 2.4 to 2.5 in both places and save the project | Verify the following error appears in the Problems pane Mapping file eclipselink-orm.xml does not have supported content for this JPA Platform |
405200 | [API] new public query-related interfaces are misplaced | Download latest build and open eclipse\plugins\org.eclipse.jpt.jpa.core .jar file | Verify the following class files are in this .jar file JavaNamedStoredProcedureQuery2_1, JavaQueryContainer2_1, JavaStoredProcedureParameter2_1, OrmNamedStoredProcedureQuery2_1, OrmQueryContainer2_1, OrmStoredProcedureParameter2_1 |
406572 | Remove jaxb binding schema from jaxb.core | Download latest build and open eclipse\plugins\jst.standard.schema jar file | Verify bindingschema xsd file appears |
... | ... | Open eclipse\plugins\jaxbcore jar file | Verify bindingschema xsd file does not appear in this file |