Community
Participate
Working Groups
we need a public API that allow import/export of EMF resource without losing links beetwen elements it should be based on works already done on copy/paste/delete/move/rename with referencing proxy
Provide an import/export function for test assets. As a continuation of enhancement 166025 (UC6: http://wiki.eclipse.org/TPTP-Test-Tools-Design-Review-166025-01112008#Core_Use_Cases), exporting a subset of test assets and then importing the subset of test assets into a new workspace (e.g. missing test assets)). This function requires UC5 (http://wiki.eclipse.org/TPTP-Test-Tools-Design-Review-166025-01112008#Core_Use_Cases), provide fall-back error handling for modifications done to test assets outside of the Test Perspective/Test Navigator (e.g. deleting a referenced test asset on the local file system). Jerome, please provide a sizing.
There is an additional requirement for Export feature: <quote> With SOA, we would like to have the ability to perform custom actions before writing each dependency to the export file. Also,our testsuites have dependencies with "in memory data". This dependencies must not be shown to the user in the wizard, but they need to be dumped in a file during the export phase. During the import phase, we need to recognize these "dump files" to be able to re-integrate the data into memory. </quote> Another example is custom code java files related to a test. These files are not displayed in the TestNav but need to be taken with master test when it is exported. When Export (or Import) wizard displays dependencies to be collected with master file, it needs to allow client code hooks to be called to provide more dependent files. These files may not have correspondent ProxyNode in Test Navigator, which is the most important thing. Hooks need to be able to display name/description of the handled file, as well as be called for custom processing (see quote above).
lots of thinking and coding is needed estimated time : around 3 to 4 week
No longer required.
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.
