Community
Participate
Working Groups
Build ID: I20070410-1043 Steps To Reproduce: 1. Start the workbench 2. From the File menu choose Import->Symptom Catalog file, the Import Symptom Catalog File wizard opens 3. Choose one of the Remote host options 4. Choose a folder where the file will be imported and a file name or accept the default name 5. Choose the WAS importer and a symptom db format (do the import for both Symptom0.1 and Symptom 2.0). Note that the WAS importer will import only WAS4.0 or WAS5.0 into both symptom 0.1 and symptom2.0 formats. 6. Finish the wizard 7. Verify that when importing the WAS4 remote symptom catalog into symptom2.0 format, recommendations are created for most of the symptom definitions. Verify also that the XPath match patterns are syntactically correct. Compare the results of importing the WAS4 remote symptom catalog into symptom 0.1 and symptom 2.0 formats by browsing through the records in the editors. 8. Select the imported symptom 2.0 format catalog in your workspace, right click and select Export->Profiling and Logging->Symptom catalog. 9. Select the TPTP symptom catalog exporter and select as the target format Symptom 2.0 format. 10. Type in the name of the destination file , c:\exportedSymptom2.xml for example and click Finish. 11. Verify that an XML file is created and the content of the XML is the same as the source file in the workspace. 12. Select again from the workbench's main menu Import->Profiling and Logging->Symptom catalog. 13. In the wizard select the Symptom 2.0 XML file that you have just exported locally (c:\exportedSymptom2.xml), then Symptom 2.0 Importer and Symptom2.0 as the target file. 14. Import the symptom catalog XML file into the workspace and verify it has the same content as the one imported at step 6. Results: The Symptom Catalog file is not getting import properly and can not be edited in the editor.Symptom definitions are not getting imported while import on local system. More information: Following testcases automation affected as a result of this bug. SymDB_Import_SymptomDB.testsuitetestcases: SymDB_Import_SymptomDB.ImportSymptomDB_1 SymDB_Import_SymptomDB.ImportSymptomDB_2 SymDB_Import_SymptomDB.ImportSymptomDB_3 SymDB_Import_SymptomDB.ImportSymptomDB_4 SymDB_Import_SymptomDB.ImportSymptomDB_5
I don't know what could have gone wrong in the driver that you have used, but I notice it's apretty old driver. I have tested using TPTP-4.4.0-200704261104 and everything works fine. Retest with a newer driver and reopen te defect if you find any issues.
Updated target to match the iteration when this defect was processed
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
