Abstract: A super junction structure includes a substrate, wherein the substrate has a first conductivity type. The super junction structure includes an epitaxial layer over the substrate, wherein the epitaxial layer has a second conductivity type opposite the first conductivity type. The super junction structure further includes a bury layer between the epitaxial layer and the substrate, wherein the bury layer has the second conductivity type. The super junction structure further includes a conductive pillar in the epitaxial layer, wherein the conductive pillar has the first conductivity type, sidewalls of the conductive pillar are angled with respect to a top-most surface of the epitaxial layer, a bottom surface of the conductive pillar is rounded, and a top-most surface of the conductive pillar is coplanar with the top-most surface of the epitaxial layer.

Abstract: Techniques are provided for analyzing testing coverage of one or more software modules to provide process coverage statistics. The techniques include obtaining one or more coverage measures from a test specification document, performing a trace on each of the one or more coverage measures during a test, analyzing each trace to generate a run-time service choreography model for a process, wherein the model includes each of one or more service choreography patterns occurring in the process, and using the model to provide statistical data on test coverage according to a process definition.

Abstract: The present invention provides a service testing method and system using a surrogate. The service testing method comprises steps of: generating, according to service description of a service to be simulated, a service-specific surrogate for said service to be simulated; deploying the generated service-specific surrogate onto a runtime system; specifying a test case by referring to the generated service-specific surrogate, wherein said test case comprises test configuration; and setting, according to the test configuration, a configuration option of the deployed surrogate on the runtime system. In the service testing method and system according to the present invention, parameters of the surrogate are dynamically configured without necessity of rewriting and deployment, thereby reducing the burden of designing and generating Mock objects.

Abstract: A method, system and apparatus for generating test data for web services testing load a selected file describing one or more web services operations into memory, select an operation specified in said loaded file, and identify one or more fields used in said operation. The one or more fields are customized and the customization is validated. Generation rules are configured and one or more variations of the fields are generated.

Abstract: A method for unit testing of business processes for Web services, including steps of mapping the Web service description language (WSDL) elements of a process under test and its partner processes into equivalent Object-Oriented language (OO) elements, and performing testing on the process under test based on Object-Oriented unit testing frameworks. Each Web service interface of the process under test and its partner processes is mapped into an equivalent OO interface, partner stubs are generated on basis of the OO interfaces of the partner processes, WSDL binding and service port information are defined for the generated partner stubs, test cases are formed which contain test logic describing the service invocations between the process under test and its partner processes, and the test cases are executed, wherein the partner stub and its associated mock object collectively implement the service of a corresponding partner process.

Abstract: A method, system and apparatus for generating test data for web services testing load a selected file describing one or more web services operations into memory, select an operation specified in said loaded file, and identify one or more fields used in said operation. The one or more fields are customized and the customization is validated. Generation rules are configured and one or more variations of the fields are generated.

Abstract: A method and apparatus for detecting an anomalistic data record. The method includes the steps of mining a data rule from a verified data record set in accordance with a mining rule, checking data records in an unverified data record set in accordance with the mined data rule and determining a data record unconformable to the mined data rule as an anomalistic data record. The apparatus includes a mining device configured to mine a data rule from a verified data record set in accordance with a mining rule and a checking device configured to check a data record in an unverified data record set in accordance with the mined data rule and to determine a data record unconformable to the mined data rule as an anomalistic data record.

Abstract: A method and an apparatus for generating test cases of a software system. The method includes the steps of: tracing a user request to acquire IT events related to each service and/or component invocation; forming IT transactions based on correlation information in IT events; correlating said IT transactions based on predetermined correlation rules, in order to form a business transaction; and extracting from the business transaction a business transaction pattern corresponding to said business transaction. The method further includes generating test cases of a software system based on the generated business transaction pattern. The apparatus includes hardware for accomplishing the foregoing method steps.

Abstract: A method (which can be computer implemented) for analyzing test coverage of distributed processes includes the steps of identifying at least one of the processes that is invoked by a test case, mapping at least a portion of the test case to a plurality of specific test paths in the at least one of the processes, and identifying given ones of the test paths as possibly relevant in at least one of the processes, if the test paths are not infeasible.

Abstract: Techniques are provided for analyzing testing coverage of one or more software modules to provide process coverage statistics. The techniques include obtaining one or more coverage measures from a test specification document, performing a trace on each of the one or more coverage measures during a test, analyzing each trace to generate a run-time service choreography model for a process, wherein the model includes each of one or more service choreography patterns occurring in the process, and using the model to provide statistical data on test coverage according to a process definition.

Abstract: The present invention provides a service testing method and system using a surrogate. The service testing method comprises steps of: generating, according to service description of a service to be simulated, a service-specific surrogate for said service to be simulated; deploying the generated service-specific surrogate onto a runtime system; specifying a test case by referring to the generated service-specific surrogate, wherein said test case comprises test configuration; and setting, according to the test configuration, a configuration option of the deployed surrogate on the runtime system. In the service testing method and system according to the present invention, parameters of the surrogate are dynamically configured without necessity of rewriting and deployment, thereby reducing the burden of designing and generating Mock objects.

Abstract: A method for unit testing of business processes for Web services, including steps of mapping the Web service description language (WSDL) elements of a process under test and its partner processes into equivalent Object-Oriented language (OO) elements, and performing testing on the process under test based on Object-Oriented unit testing frameworks. Each Web service interface of the process under test and its partner processes is mapped into an equivalent OO interface, partner stubs are generated on basis of the OO interfaces of the partner processes, WSDL binding and service port information are defined for the generated partner stubs, test cases are formed which contain test logic describing the service invocations between the process under test and its partner processes, and the test cases are executed, wherein the partner stub and its associated mock object collectively implement the service of a corresponding partner process.