Community
Participate
Working Groups
Provide a Java Web Service client JUnit-based test type, editor and recorder. Web Services are often functionally or unit tested by writing test code that invokes the Java Web Service client stub methods. The test code invokes the client stub methods using various parameter data and possibly the return value of the invocation to verify the correctness of the Web Service(s). This form of functional or unit testing for Web Services is independent of the transport protocol (e.g. SOAP over HTTP). The Java Web Service client stub methods are defined by the Java standard for Web Service clients and endpoints, called Java API for XML-Based RPC (JAX-RPC). These interfaces are implemented by all Java Web Service API implementations, such as Apache Axis. This enhancement involves creating a specialized TPTP test type for testing Java Web Service client stubs. A Web Services test type would require the following: -A wizard for creating empty Web Services test suites. -An editor for defining the composition (e.g. drag-n-drop methods defined in WSDL file(s)) and execution behavior of Web Services test suites. The Web Services test suite editor would allow test authors to define verification points and utilize data pools. -A recorder, based on the generic Java API recorder (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=119688), to generate Web Services test suites from test code invocations of Java Web Service client stub methods. Also, a component is required for generating Web Services test suites from the recording file generated by the recorder. -A code generator for creating JUnit-based test code based on the Web Services test suite for local and remote execution using the existing TPTP JUnit execution harness.
Reassigning to Paul.
P2 Highly desirable and planned for this release, but not stop ship Theme(s) for this enhancement: -Appealing to the Broader Community
Correcting version for this enhancement (defaulting to the current release). See http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html for more information.
Correction: Future is a valid version for this enhancement based on http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html. As such, the implicit assumption is that is enhancement is of a lower priority. If incorrect, the originator should correct the version.
Updating target to future as requested by the PMC. Enhancements are targeted to future if not in plan for the current release.
Correcting priority since not a 4.5 candidate enhancement (see http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html).
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).
Closing.
