KR101579029B1 - Application programming interface testing services - Google Patents

Abstract

Technologies and implementations that provide application programming interface testing services for transmitting data center services.

Description

[0001] APPLICATION PROGRAMMING INTERFACE TESTING SERVICES [0002]

Unless otherwise indicated herein, the approaches described in this section are not prior art to the claims in this application, and are not considered to be prior art by inclusion in this section.

In a customer's data center deployment, various application programming interface calls may be used. Generally, when transferring from one data center to another, it is important to know which application programming interface calls in use at the origin data center may be available at the destination data center, It may be useful to know if it may not be available. In general, it may be difficult to determine which application programming interface calls may be in use at the origin data center.

In various embodiments, the present disclosure describes exemplary methods of providing an application programming interface testing service. Exemplary methods include determining application programming interface calls used by the service in the origin data center, converting each of the application programming interface calls into a test segment to generate test segments, and testing the application programming interface test Wherein the application programming interface test module comprises forming the application programming interface test module comprising a plurality of test segments.

In various embodiments, the present disclosure also describes exemplary machine-readable non-volatile media. Exemplary machine-readable non-volatile media include, when executed, causing the device to determine application programming interface calls used by a service in an originating data center, transforming each application programming interface call into a test segment to generate test segments And forming an application programming interface test module for a target data center, wherein the application programming interface test module comprises an application programming interface testing service by forming the application programming interface testing module, comprising a plurality of test segments, Or < / RTI >

In various embodiments, the present disclosure also describes exemplary devices. Exemplary devices, when executed, allow a device to determine application programming interface calls used by a service in an origin data center, convert each of the application programming interface calls into test segments to generate test segments, Forming an application programming interface test module for a data center, the application programming interface test module comprising instructions for providing an application programming interface testing service by forming the application programming interface testing module, comprising a plurality of test segments, And a processor coupled to the machine-readable medium for executing the instructions.

The above summary is illustrative only and may not be intended to be limiting in any way. In addition to the exemplary aspects, embodiments, and features described above, additional aspects, embodiments, and features will become apparent with reference to the drawings and the following detailed description.

The subject matter is particularly pointed out and distinctly claimed in the concluding portion of the specification. The foregoing and other features of the present disclosure will become more fully apparent from the following description taken in conjunction with the accompanying drawings and the appended claims. BRIEF DESCRIPTION OF THE DRAWINGS These drawings are merely illustrative of several embodiments in accordance with the present disclosure and, therefore, should not be construed as limiting the scope thereof, the present disclosure will be described in further detail and with reference to the use of the accompanying drawings .
Figure 1 shows a flow chart of an example method of providing an application programming interface testing service.
Figure 2 shows a flow diagram of an example method of determining application programming interface calls used by a service in an origin data center.
Figure 3 shows a flow diagram of an example method of determining application programming interface calls used by a service in an origin data center.
Figure 4 shows a block diagram of an example system for providing an application programming interface testing service.
5 shows a block diagram of an example system for providing an application programming interface testing service.
Figure 6 shows an example computer program product.
Figure 7 illustrates a block diagram of an example computing device in which the whole is arranged according to at least some embodiments of the present disclosure.

The subject matter is particularly pointed out and distinctly claimed in the concluding portion of the specification. The foregoing and other features of the present disclosure will become more fully apparent from the following description taken in conjunction with the accompanying drawings and the appended claims. BRIEF DESCRIPTION OF THE DRAWINGS These drawings are merely illustrative of several embodiments in accordance with the present disclosure and, therefore, should not be construed as limiting the scope thereof, the present disclosure will be described in further detail and with reference to the use of the accompanying drawings .

The following description sets forth various examples together with specific details in order to provide a thorough understanding of the claimed subject matter. However, it will be understood by those of ordinary skill in the art that the claimed subject matter may be practiced without some or more of the specific details disclosed herein. Moreover, in some instances, well-known methods, procedures, systems, components, and / or circuits have not been described in detail in order to avoid unnecessarily obscuring the claimed subject matter.

In the following detailed description, reference is made to the accompanying drawings which form a part of this document. In the figures, similar symbols generally identify similar components unless context dictates otherwise. The illustrative embodiments set forth in the description, drawings and claims are not meant to be limiting. Other embodiments may be used and other changes may be made without departing from the spirit or scope of the subject matter disclosed herein. As described generally herein and as illustrated in the Figures, aspects of the present disclosure may be arranged, substituted, combined, and designed in a wide variety of different configurations, all of which are expressly contemplated and form part of the present disclosure.

This disclosure relates, among other things, to methods, devices, systems, and computer-readable media related to providing an application programming interface testing service for transmitting data center services.

Typically, data center customers may use services in the data center. A service may include various subservices such as data storage, communications, data center based applications, hosted applications, and the like. In some instances, the applications or their software components may use application programming interface (API) calls and / or web service protocols such as simple object access protocol (SOAP) or representational state transfer (REST). In general, an API may provide specifications for use by applications or application components that represent available functions or processes, and the like. API calls may include calls such as commands (with or without arguments and / or other related data) that may call one or more functions or processes marked as supported by the API. In some examples, the web service protocol may provide a protocol for exchanging structured information, including API calls.

Also, in some instances, a data center customer may seek to move from one data center to another for lower cost, better service, or the like. As will be appreciated, if a datacenter customer moves from one datacenter to another, which API calls may be in use at the origin datacenter (i.e., the customer's current datacenter) It may be difficult to predict whether or not they may be supported in a target data center or data centers (i.e., a data center or centers in which a customer may be considering a move). In general, the embodiments discussed herein are directed to providing a method and system for application programming that enables data center customers to make API calls that are used in their services and to generate test modules that test at least a portion of such API calls in one or more target data centers. It can also provide interface testing services. In some instances, an origin data center or a third party computing device may send a test module to a target data center and receive test results based on a test module running in the target data center. Based on the test results, the data center customer may better evaluate the potential data center movement and may better evaluate the potential target data centers. In some instances, the discussed application programming interface testing service may be performed by a third party service provider, such as a data center services broker or the like. The discussed application programming interface testing services may also provide user confidence in which programs, applications, or other subservices that may eliminate fear, uncertainty or suspicion of data center migration may be performed at the destination data center have. In addition, using programs, applications, or other subservices that may not be fully supported in the destination data center, the customer may employ contingency planning, such as software upgrades, to ensure smooth migration.

1 illustrates a flow diagram of an exemplary method 100 for providing an application programming interface testing service arranged in accordance with at least some embodiments of the present disclosure. In general, the method 100 may be performed by any suitable device, devices, or systems, such as those discussed herein. In some instances, the method 100 may be performed by a data center. In some instances, the method 100 may be performed by data center resources or resources. In some instances, the method 100 may be performed by a virtual machine, a data center cluster, one or more network processors, one or more routers, gateway systems, data loss prevention systems, and the like. In some instances, the method 100 may be performed by a virtual machine in the data center. In some instances, the method 100 may be performed by a third party resource, such as a third party computing device.

The method 100 describes various functional blocks or actions that may be described as processing steps, functional objects, events and / or acts, etc., that may be performed by hardware, software, and / or firmware. Numerous alternatives to the functional blocks shown in Figure 1 may be implemented in various implementations. For example, intervening actions not shown and / or additional actions not shown may be employed, and / or some of the actions shown may be eliminated without departing from the scope of the claimed subject matter. The method 100 may include one or more functional operations represented by one or more blocks 105, 110, 115, 120, 125, 130, 135, 140, and / The process of method 100 may begin at block 105.

At block 105, "Determining application programming interface calls used by the origin data center," one or more application programming interface calls used by the originating datacenter service may be determined. In general, one or more application programming interface calls used by a service in an origin data center may be determined using any suitable technique or techniques. In some instances, one or more application programming interface calls used by the origin data center may be generated by extracting application interface calls from messages captured at network processors as discussed further with respect to FIG. 2 and elsewhere herein May be determined. In some instances, one or more application programming interface calls used by the origin data center may be determined by evaluating the code repository to detect application programming interface calls as discussed further with respect to FIG. 3 and elsewhere herein have.

In general, application programming interface calls may include any application programming interface calls. As discussed, in some examples, an application programming interface call may invoke one or more functions or processes indicated as supported by the application programming interface (such as having arguments and / or other associated data ) ≪ / RTI > command. In some instances, the application programming interface calls may include a hypertext transfer protocol get request, a hypertext transfer protocol put request, a key-value save command, a messaging call, a queuing call, a remote save call, a content delivery, Delivery requests to the network, management commands to the content delivery network, and the like. In some instances, an application programming interface call may be implemented using a simple object access protocol (SOAP). In general, a simple object access protocol may provide a structure for exchanging information, and may depend on extensible markup language (XML) or JavaScript Object Notation (JSON) for its message format. In some instances, application programming interface calls may be implemented using representational state transfer (REST), which may provide a software architecture for distributed systems.

In general, any number of application programming interface calls may be used by customer service in the data center. In some instances, the number of application programming interface calls used by the customer service may range from about 100 to about 1,000. In some instances, the number of application programming interface calls used by the customer service may range from about 1,000 to about 10,000. Determining the application programming interface calls used in the origin data center may provide a database or a list of mixes of application programming interface calls utilized by the applications in use of the customer's service. In some instances, a mix of application programming interface calls utilized by applications in use may be added to new applications, programs, or subservices over time, even if known at set-up of customer service It may change over time.

In general, a service at an origin data center may include any suitable customer service or services, and may include a single service, various subservices, one or more virtual machines, and the like. In some instances, the service may include an application in use. In some instances, a service may include one or more data center-based applications, one or more hosted applications, one or more data storage services, one or more communication services, and the like. In some instances, customer service in the data center may be considered for customer deployment, data center deployment, cloud computing deployment, and the like. The process of method 100 may continue at block 110.

In block 110, "Converting Application Programming Interface Calls to Test Segments ", one or more application programming interface calls may be converted into test segments. In some examples, each of the plurality of application programming interface calls may be transformed into a test segment to generate a plurality of test segments. In some instances, some application programming interface calls may be combined into a single test segment. In some instances, one application programming interface call may be split into two or more test segments. As discussed further herein, in some instances, duplicate application programming interface calls may be discarded and test segments may be generated only for substantially unique application programming interface calls. In general, test segments may include any suitable test segments. In some instances, the test segment may include an application programming interface setup call. In some examples, the test segment may include an application programming interface call in an error detection loop configured to record whether the application programming interface call correctly executed or returned an error. In some examples, the test segment may include an application programming interface (API) in an error detection loop that includes a header and / or a footer so that the error detection loop can be configured to record whether the application programming interface call correctly executed or returned an error. It may also include a call.

As discussed, in some examples, the test segment may include an error correction loop in the code, which may record the application programming interface call correctly executed, returned an error, or in some way not returning a confirmation, Lt; RTI ID = 0.0 > a < / RTI > test segment. In some instances, the test segment may include a head or footer, or may utilize a specific error detection code in the target data center. The following sample code (1) illustrates an exemplary test segment that may record test results on the console (in practice, the test results may be written to a report file, for example).

In some instances, for successful application programming interface calls, the test segment may capture additional information, such as the elapsed time to execute, so that direct comparisons between the origin data center and the target data center can be made. The process of method 100 may continue at block 115.

In block 115, "forming an application programming interface test module, " an application programming interface test module may be formed based on test segments. In general, the application programming interface test module may be formed using any suitable technique or techniques. In some instances, the application programming interface test module may include each of the plurality of test segments described above. In some instances, an application programming interface test module may be intended for one or more target data centers as discussed further herein. In some instances, an application programming interface test module may be considered as a compatibility test program, a compatibility test module, and the like. In some instances, an application programming interface test module may provide substantially faster testing of one or more target data centers. The sample pseudo-code (2) shows an example part of the test module.

for each (APIs_to_test)

{

 Record API under test in report;

 Send API test message;

 Wait a reasonable time if no response is received;

 Catch any errors [e.g., code (1) shown above] or record functional response;

 Record end of API test in report;

 Get next API to test;

}

(2)

As discussed, in some instances, pseudo-code 2 or the like may be utilized to form a test module. As discussed below with respect to block 120, in some instances, a test module may be transmitted entirely to test a test module. In other examples, each test segment may be sent to a target data center for testing. In some instances, test segments may be transmitted as simple object access protocol messages. In some instances, a group or subset of test modules may be sent to the target data center for testing. The process of method 100 may continue at block 120.

In block 120, "Send application programming interface test module to target data center ", an application programming interface test module may be transmitted to one or more target data centers for execution in one or more target data centers. In some instances, the application programming interface test module may be transmitted to a single target data center. In some instances, an application programming interface test module may be transmitted to multiple target data centers so that target data centers can be compared, as discussed further below and elsewhere herein for block 130. In some instances, the application programming interface test module may be transmitted simultaneously or substantially concurrently to multiple target data centers. In general, the application programming interface test module may be transmitted using any suitable technique or techniques using any suitable communication channel. In some instances, the application programming interface test module may be transmitted over the Internet. In some instances, the application programming interface test module may be transmitted via a virtual private network (VPN). As discussed, in some examples, test segments or groups of test segments may be sent individually to one or more target data centers for testing. The process of method 100 may continue at block 125.

At block 125, Receive Test Results, one or more test results may be received. In some instances, the one or more test results may be received based at least in part on an application programming interface test module executing in the target data center. In some instances, one or more test results may be received after the application programming interface test module executes at one or more target data centers. In general, one or more test results may be received using any suitable technique or techniques and on any suitable communication channel. In some instances, one or more test results may be received via the Internet or a virtual private network. In general, one or more test results may include test results in any suitable format. In some instances, the test results may include a plurality of test results corresponding to a plurality of test segments that may constitute an application programming interface test module. In some instances, the test results may include a test report. In some instances, a test report may include test results for each of a plurality of test segments. In general, test results may include any suitable test results for the discussed test segments. In some instances, the test results may indicate whether the test segment was successfully executed. In some instances, the test results may indicate whether the test segment has failed. In some instances, the test results may indicate whether the test segment returned an error. As discussed, in some examples, the application programming interface test module may include a hypertext transfer protocol get request. In such instances, the test results may include an indication of whether the hypertext transfer protocol get request was successful. The process of method 100 may continue at decision block 130.

Decision block 130, "other target data centers? , It may be determined whether other target data centers are tested with the application programming interface test module. If other target data centers are not being tested (i.e., only one target data center is being tested), the process of method 100 may end at block 135, as shown at "end". If other target data centers are to be tested, the process of method 100 may continue at decision block 140.

Decision block 140, "Are all targets tested?" , It may be determined whether all of the target data centers have been tested. If not all of the target data centers have been tested, the process of method 100 may continue at block 120, where the process receives and executes application programming interface test modules for each target datacenter being tested, All of the target data centers that are being tested so that the test results of the target data center of the target data center may be received may continue as described again until completion of the testing. If not all of the target data centers have been tested, the process of method 100 may continue at block 145.

At block 145, "Compare target data centers," the tested target data centers may be compared. In general, the tested target data centers may be compared using any suitable technique or techniques. In some instances, the tested target data centers may be compared to determine which data center can support the largest number of application programming interface calls. In some instances, the tested target data centers may be compared to determine which data center can support any number of priority application programming interface calls.

As discussed, the process of method 100 may be utilized to test and compare any number of target data centers. In some instances, the application programming interface test module may be transmitted to a first target data center for execution in a first target data center, and the first test results may be transmitted to a first target data center using a transmitted application programming interface test Module, and the application programming interface test module may be transmitted to the second target data center for execution in the second target data center, and / or the second test results may be received in the second target data center May be received based on the transmitted application programming interface test module to be executed. In a similar manner, the application programming interface test module may be transmitted for execution to any number of target data centers, and any number of test results may be received from the target data centers for comparison.

As discussed, the process of method 100 may return test results from one or more target data centers. In some instances, the test results may indicate whether the various application programming interface calls were successfully executed, failed, reported errors, and so on. In some instances, any reported errors may be further investigated or checked to determine more detail about the error. In some instances, the error may indicate that the application programming interface call may not be supported. In some instances, the error may indicate that an application programming interface call is supported, but one piece of data may not be delivered correctly by the application programming interface call. In some instances, the error may indicate that an application programming interface call is supported, but one piece of data may not be available at the destination data center. Such additional details and evaluation may indicate support for one or more application programming interface calls and that the code may only need to be updated, or that necessary data may need to be provided to the data center, have.

2 illustrates a flow diagram of an example method 200 for determining application programming interface calls used by a service in an origin data center, arranged in accordance with at least some embodiments of the present disclosure. In general, the method 200 may be performed by any suitable device, devices, or systems, such as those discussed herein. In some instances, the method 200 may be performed by a data center. In some instances, the method 200 may be performed by data center resources or resources. In some instances, portions of method 200 or method 200 may be performed by a virtual machine, a data center cluster, one or more network processors, one or more routers, gateway systems, data loss prevention systems, and the like. In some instances, the method 200 may be performed by a virtual machine in the data center. In some instances, the method 200 may be performed by an origin data center.

The method 200 states various functional blocks or actions that may be described as processing steps, functional operations, events and / or acts, etc., which may be performed by hardware, software, and / . A number of alternatives to the functional blocks shown in FIG. 2 may be implemented in various implementations. For example, intervening actions not shown and / or additional actions not shown may be employed, and / or some of the actions shown may be eliminated without departing from the scope of the claimed subject matter. The method 200 may include one or more functional operations as indicated by one or more blocks 210, 220, 230, 240, and / or 250. The process of method 200 may begin at block 210.

At block 210, "Capture Messages at Network Processor, " multiple messages may be captured at the network processor. In general, any suitable messages may be captured at the network processor. In some instances, the captured messages may include network messages in-operation. In some instances, the captured messages may include a simple object access protocol (SOAP) message. In some instances, the captured messages may include a representational state transfer (REST) message. In general, messages may be captured using any suitable technique or techniques. In some instances, network messages may be snooped to detect whether a network message may have an application programming interface call. In some instances, network messages may be evaluated at full line speed. In some instances, network messages may be handled by an attached service handler, which may evaluate messages in series or in batches. In general, network messages may be evaluated for any time frame for collecting application programming interface calls. In some instances, network messages may be evaluated for jobs, weeks, or months. In general, network messages may be evaluated for a duration that may capture as much usage as is necessary to capture commonly used and rarely used application programming interface calls. As discussed, in some instances, messages may be captured in one or more network processors. In some instances, the messages may be captured in a router, in dedicated hardware, in a gateway system, or in a data loss prevention system, and so on. The process of method 200 may continue at block 220.

At block 220, "Extract application programming interface calls," application programming interface calls may be extracted from the captured messages. In general, application programming interface calls may be extracted using any suitable technique or techniques. In some instances, application programming interface calls may be extracted from a simple object access protocol message. In some instances, as discussed further below, application programming interface calls may be used for inclusion in a list of application programming interface calls used by a customer's service, or for application programming interface calls previously used by a customer's service Copied, and delivered to other processes for determination as to whether or not they are included in the list of application programming interface calls. The process of method 200 may continue at decision block 230.

Decision block 230, "Is the application programming interface call similar to a previously captured call? , It may be determined whether the extracted application programming interface call may be substantially similar or identical to an already captured and / or extracted application programming interface call. In general, by any suitable technique or techniques, it may be determined whether the extracted application programming interface call may be substantially similar or identical to an already captured and / or extracted application programming interface call. In some instances, the similarity may be based on a comparison of already captured and / or extracted calls or application programming interface calls to the database. In some instances, the similarity may be based on a comparison of the programming code of the captured and / or extracted application programming interface calls. In general, the determination of whether an application programming interface call is similar to a previous application programming interface call may be biased towards including application programming interface calls. If the application programming interface call is determined to be substantially similar or identical to a previously captured and / or extracted call, then the process of the method 200 may proceed to block 250, Discard the programming interface call ". If it is determined that the application programming interface call is not substantially similar or identical to a previously captured and / or extracted call, the process of method 200 may continue at block 240.

At block 240, "Include Application Programming Interface Calls," the extracted application programming interface calls may be included in the application programming interface calls used at the originating data center. In some instances, the application programming interface calls used may be used by customers having services in the origin data center as discussed herein. In general, application programming interface calls may be included in application programming interface calls used using any suitable technique or techniques. In some instances, application programming interface calls may be added to a list of application programming interface calls, a database of application programming interface calls, and so on.

As discussed, the process of method 200 includes a comparison of captured and / or extracted application programming interface calls to previously captured and / or extracted application programming interface calls. In some instances, such comparisons may be omitted so that all captured and / or extracted application programming interface calls may be included as discussed for block 240. [ In some instances, a list of all captured and / or extracted application programming interface calls may be subsequently removed to eliminate duplicates.

FIG. 3 shows a flow diagram of an exemplary method 300 for determining application programming interface calls used by a service in an origin data center, arranged in accordance with at least some embodiments of the present disclosure. In general, the method 300 may be performed by any suitable device, devices, or systems, such as those discussed herein. In some instances, the method 300 may be performed in an understanding of the data center. In some instances, the method 300 may be performed by data center resources or resources. In some instances, the method 300 may be performed by a virtual machine, a data center cluster, one or more network processors, one or more routers, gateway systems, data loss prevention systems, and the like. In some instances, the method 100 may be performed by a virtual machine in the data center. In some instances, the method 100 may be performed by an origin data center.

The method 300 states various functional blocks or actions that may be described as processing steps, functional operations, events and / or acts, etc., which may be performed by hardware, software, and / . Many alternatives to the functional blocks shown in FIG. 3 may be implemented in various implementations. For example, intervening actions not shown and / or additional actions not shown may be employed, and / or some of the actions shown may be eliminated without departing from the scope of the claimed subject matter. The method 300 may include one or more functional operations as indicated by one or more blocks 310 and / or 320. The process of method 300 may begin at block 310.

At block 310, "Evaluate code repositories to detect code-level application programming interface calls", a code repository may be evaluated to detect code-level application programming interface calls. In general, a code repository may be evaluated to detect code-level application programming interface calls using any suitable technique or techniques. In some instances, evaluating a code repository may include textual searches for code, such as code repositories for application programming interface calls or code representing application programming interface calls. The process of method 300 may continue at block 320.

At block 320, "Including code-level application programming interface calls," code-level application programming interface calls may be included in application programming interface calls used in the originating data center. In some instances, the application programming interface calls used may be used by customers having services in the origin data center as discussed herein. In general, application programming interface calls may be included in application programming interface calls used using any suitable technique or techniques. In some instances, application programming interface calls may be added to a list of application programming interface calls, a database of application programming interface calls, and so on.

As discussed, the method 200 may include capturing and / or extracting application programming interface calls, and the method 300 may include evaluating a code repository to detect application programming interface calls It is possible. In some instances, the processes of method 200 and method 300 may be combined to determine the application programming interface calls used by the customer's service in the data center. In some instances, the process of method 200 may be performed first. In some instances, the process of method 300 may be performed first. In some instances, the processes may be performed simultaneously or substantially concurrently. As discussed for method 200, in some instances, duplicate application programming interface calls may be removed from the list of in-use application programming interface calls used by the customer's service.

The techniques describe methods for determining application programming interface calls used by a customer's service in a data center. In some instances, the techniques described may use message redundancy and low-level access to determine common application programming interface calls so that programming libraries or custom code for each data center is not required. Such techniques may provide advantages at low cost, speed, and scalability. In addition, a determined list of application programming interface calls used by a customer's service (or services of multiple customers) in the data center may be used as a source for other data centers, for example, For example, to check if the application is supported, to improve support for the ability of widely used application programming interface calls, and the like.

FIG. 4 illustrates a block diagram of an exemplary system 400 for providing application programming interface testing services arranged in accordance with at least some embodiments of the present disclosure. As shown, the system 400 may include an origin data center 410 having a service 412 that includes application programming interface calls 414. The system 400 may also include a target data center 420 in communication with the origin data center 410 via a connection 430.

In general, the origin data center 410 may include a service 412 for a customer, or any suitable data center having multiple services for one or more customers. In some instances, the origin data center 410 may include computers, servers, server systems, data storage systems, communication systems, computing clusters, and / or incidental peripheral systems. In some instances, data center 410 may be implemented in a cloud computing environment. In some instances, data center 410 may include one or more network processors, one or more routers, gateway systems, data loss prevention systems, and the like. In some instances, data center 410 may include databases or databases that may serve as repositories for code repositories associated with services 412. In general, the services 412 may be implemented in the data center 410 in any suitable manner. As will be appreciated, the origin data center 410 may include any number of services 412 corresponding to any number of customers serviced by the origin data center 410. In general, application programming interface calls 414 may include any application programming interface calls as discussed herein.

In general, target data center 420 may include any suitable data center that may execute application programming interface test modules as discussed herein. In some instances, the target data center 420 may be a computer system, such as computers, servers, server systems, data storage systems, communication systems, computing clusters, network processors, databases, and / . In some instances, the target data center 420 may be implemented in a cloud computing environment. In general, the application programming interface test module may be executed in the target data center 420 in any suitable manner. As shown, in some examples, the system 400 may include one target data center. In some instances, the system 400 may include multiple target data centers for testing as discussed herein.

As shown, the origin data center 410 and the target data center 420 may be in communication via the connection 430. [ In general, connection 430 may include any suitable communication connection. In some instances, the communication connection may comprise a virtual private network (VPN) tunnel. In some instances, the communication connection may comprise a management connection. In some instances, the communication connection may be through the Internet.

As discussed herein, in some instances, an application programming interface testing service may be provided. In some instances, the application programming interface testing service may be provided by the origin data center. For example, the application programming interface calls 414 used by the service 412 may include, for example, extracting from the captured messages at the network processor (as discussed with respect to FIG. 2) and / May be determined at the origin data center 410 using any of the techniques discussed herein, such as by evaluating a code repository (as discussed above). In some instances, the application programming interface calls may be transformed into test segments, an application programming interface test module may be formed, an application programming interface test module may be sent, and test results may be sent to the origin data center 410 Lt; / RTI > In some instances, target data center 420 may receive and execute application programming interface test modules or test segments as discussed herein.

FIG. 5 illustrates a block diagram of an exemplary system 500 for providing application programming interface testing services arranged in accordance with at least some embodiments of the present disclosure. As shown, the system 500 may include an origin data center 410 having a service 412 that includes application programming interface calls 414 as discussed with respect to FIG. 4 and elsewhere herein. have. The system 500 may also include a target data center 420, as discussed with respect to FIG. 4 and elsewhere herein. The system 500 may also include a third party resource 510 that is in communication with the target data center 420 by a connection 530 in communication with the origin data center 410 by a connection 520.

In general, the third party resource 510 may include any suitable computing device or devices. In some instances, third party resources 510 may include computers, servers, server systems, data storage systems, communication systems, computing clusters, and / or incidental peripheral systems, and the like. As shown, the third party resource 510 may be communicating with the originating data center 410 by connection 520 and communicating with the target data center 420 by connection 530. In general, connections 520 and 530 may include any suitable communication connections. In some instances, one or both communication connections may include a virtual private network (VPN) tunnel. In some instances, one or both communication connections may include a management connection. In some instances, one or both communication connections may be through the Internet.

As discussed herein, in some instances, an application programming interface testing service may be provided. In some instances, the application programming interface testing service may be provided by the third party resource 510. For example, the application programming interface calls 414 used by the service 412 may be communicated via the software or commands provided by the third party resource 510 and via a network (e. G., As discussed with respect to FIG. 2) As determined at the origin data center 410 using any of the techniques discussed herein, such as by extracting from the captured messages at the processor and / or evaluating the code repository (as discussed with respect to FIG. 3) It is possible. In some instances, the application programming interface calls may be transformed into test segments, an application programming interface test module may be formed, an application programming interface test module may be sent, Lt; / RTI > In some instances, third party resources 510 may be managed / managed or operated by a party providing information or assistance, etc., for customers to migrate between data centers. In some instances, the third party resource 510 may be managed and / or operated by a data center or a cloud services broker.

Figure 6 illustrates an example computer program product 600 arranged in accordance with at least some embodiments of the present disclosure. The computer program product 600, when executed, may include a machine-readable non-volatile medium storing a plurality of instructions that cause the machine to provide an application programming interface testing service in accordance with the processes and methods discussed herein . The computer program product 600 may include a signal bearing medium 602. The signal bearing medium 602 may include one or more machine-readable instructions 604 that, when executed by one or more processors, may enable the computing device to operatively provide the functionality described herein, have. In various instances, some or all of the machine-readable instructions may be used by the devices discussed herein.

In some instances, machine-readable instructions 604 include instructions that, when executed, cause the device to provide instructions for providing an application programming interface testing service by determining a plurality of application programming interface calls used by the service in the originating datacenter . In some instances, machine-readable instructions 604, when executed, cause the device to provide an application programming interface testing service by converting each of a plurality of application programming interface calls into test segments to generate a plurality of test segments ≪ / RTI > In some examples, machine-readable instructions 604, when executed, cause the device to form an application programming interface test module for a target data center, wherein the application programming interface test module includes each of a plurality of test segments And providing the application programming interface testing service by forming the application programming interface test module. In some instances, the machine-readable instructions 604, when executed, provide the application programming interface testing service by sending the application programming interface test module to the target data center for execution on the target data center ≪ / RTI > In some instances, the machine-readable instructions 604, when executed, cause the device to perform one or more of the following steps, by receiving one or more test results based at least in part on a transmitted application programming interface test module, And may include instructions to provide a programming interface testing service. In some instances, the machine-readable instructions 604, when executed, provide the application programming interface testing service by sending the application programming interface test module to the target data center for execution on the target data center ≪ / RTI > In some instances, the machine-readable instructions 604, when executed, cause the device to receive one or more test results based, at least in part, on a transmitted application programming interface test module executed in the target data center, Wherein the programming interface test module includes a hypertext transfer protocol put request and wherein the one or more test results include an indication that the hypertext transfer protocol get request was successful, And may include instructions to provide a testing service. In some instances, the machine-readable instructions 604, when executed, cause the device to perform one or more of the application programming interface testing by comparing the one or more test results to one or more second test results received from the second target data center Services to provide the service.

In some implementations, the signal bearing medium 602 includes a computer readable medium 606 such as but not limited to a hard disk drive, a compact disk (CD), a digital versatile disk (DVD), a digital tape, It is possible. In some implementations, the signal bearing medium 602 may include a recordable medium 608 such as but not limited to memory, read / write (R / W) CDs, R / W DVDs, In some implementations, the signal bearing media 602 may include communication media 610, such as but not limited to digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, . ≪ / RTI > In some instances, the signal bearing medium 602 may comprise a machine readable non-volatile medium.

FIG. 7 illustrates a block diagram of an exemplary computing device 700, arranged in accordance with at least some embodiments of the present disclosure. In various instances, the computing device 700 may be configured to provide the application programming interface testing services discussed herein. In one example basic configuration 701, computing device 700 may include one or more processors 710 and system memory 720. Memory bus 730 may be used to communicate between processor 710 and system memory 720.

Depending on the desired configuration, the processor 710 may be of any type including, but not limited to, a microprocessor (μP), a microcontroller (μC), a digital signal processor (DSP), or any combination thereof. Processor 710 may include one or more levels of caching, such as a level 1 cache 711 and a level 2 cache 712, a processor core 713, and registers 714. The processor core 713 may comprise an arithmetic logic unit (ALU), a floating point unit (FPU), a digital signal processing core (DSP core), or any combination thereof. The memory controller 715 may also be used with the processor 710 or, in some implementations, the memory controller 715 may be an internal portion of the processor 710. [

Depending on the desired configuration, the system memory 720 may be any type including, but not limited to, volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.) have. The system memory 720 may include an operating system 721, one or more applications 722, and program data 724. The application 722 may include an API testing application 723 that may be arranged to perform the functions, actions, and / or actions described herein, including the functional blocks, actions, and / . The program data 724 may include API testing data 725 for use with the API testing application 723. In some example embodiments, the application 722 may be arranged to operate with the program data 724 on the operating system 721. This described basic configuration is shown in Fig. 7 by these components in dotted line 701.

The computing device 700 may have additional features or functionality and additional interfaces that facilitate communication between the basic configuration 701 and any desired devices and interfaces. For example, the bus / interface controller 740 may be used to facilitate communication between the base configuration 701 and the one or more data storage devices 750 via the storage interface bus 741. The data storage devices 750 may be removable storage devices 751, non-removable storage devices 752, or a combination thereof. Examples of removable and non-removable storage devices include, but are not limited to, flexible disk drives and magnetic disk devices such as hard disk drives (HDD), compact disk (CD) drives, or digital versatile disk , Solid state drives (SSD), and tape drives. Illustrative computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. . ≪ / RTI >

The system memory 720, the removable storage device 751, and the non-removable storage device 752 are all examples of computer storage media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices , Or any other medium that may be accessed by computing device 700 and used to store the desired information. Any such computer storage media may be part of device 700.

The computing device 700 also facilitates communication from the various interface devices (e.g., output interfaces, peripheral interfaces, and communication interfaces) to the base configuration 701 via the bus / interface controller 740 And an interface bus 742 for interfacing with an external device. Exemplary output interfaces 760 include a graphics processing unit 761 and an audio processing unit 762, which may be configured to communicate with various external devices, such as a display or speakers, via one or more A / V ports 763. [ ). Exemplary peripheral interfaces 770 may include input devices (e.g., a keyboard, mouse, pen, voice input device, touch input device, etc.) or other peripheral devices A serial interface controller 771 or a parallel interface controller 772, which may be configured to communicate with external devices such as, for example, a printer, a scanner, and the like. The example communication interface 780 includes a network controller 781 that may be arranged to facilitate communication with one or more other computing devices 783 via network communication via one or more communication ports 782 . A communication connection is one example of a communication medium. Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and may include any information delivery media . A "modulated data signal" may be a signal having one or more of its set of features set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared (IR), and other wireless media. The term computer-readable media as used herein may include both storage media and communication media.

The computing device 700 may be a cellular phone, a mobile phone, a tablet device, a laptop computer, a personal digital assistant (PDA), a personal media player device, a wireless web- (Or mobile) electronic device, such as a hybrid device, including a < RTI ID = 0.0 > The computing device 700 may also be implemented as a personal computer, including laptop computers and non-laptop computer configurations. The computing device 700 may also be implemented as part of a wireless base station or other wireless system or device.

Some portions of the above detailed description are presented by algorithms or symbolic representations of operations on data bits or binary digital signals stored in a computing system memory, such as a computer memory. These algorithmic descriptions or representations are examples of techniques that are used by ordinary artisans in data processing techniques to convey the nature of their work to other conventional artisans of the art. The algorithm is considered here to be a consistent sequence or similar processing of the operations that result here and generally in the desired result. In this context, operations or processing involves physical manipulation of physical quantities. Typically, but not necessarily, such quantities may take the form of electrical or magnetic signals that may be stored, transmitted, combined, compared, or otherwise manipulated. It has proven convenient sometimes to refer to such signals as bits, data, values, elements, symbols, characters, terms, numbers, numbers, etc., for reasons of normal use. It should be understood, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels. Unless specifically stated otherwise, discussions utilizing terms such as "processing", "computing", "computing", "decision" Refers to actions or processes of a computing device that manipulates or transforms data represented as physical electronic or magnetic quantities within storage devices, transmission devices, or display devices of a computing device.

The foregoing detailed description has described various embodiments of devices and / or processes using block diagrams, flowcharts and / or illustrations. Each such function and / or operation in such block diagrams, flowcharts, or illustrations, as long as such block diagrams, flowcharts, and / or illustrations contain one or more functions and / , Firmware, or virtually any combination thereof, as will be appreciated by those of ordinary skill in the art. In some embodiments, several portions of the subject matter described herein may be implemented through custom semiconductors (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), or other integrated formats have. However, those of ordinary skill in the art will appreciate that some aspects of the embodiments disclosed herein may be embodied in whole or in part as one or more computer programs running on one or more computers (e.g., As one or more programs executing on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or indeed any combination thereof, in an integrated circuit It will be appreciated that the invention can be implemented in a manner that is well within the skill of the ordinary artisan in view of this disclosure in designing the circuit and / or writing the code for the software and / or firmware. It will also be appreciated by those of ordinary skill in the art that the mechanisms of the subject matter described herein may be deployed as a program product in a variety of forms and that exemplary implementations of the subject matter described herein may be embodied in a signal bearing medium But will apply regardless of the particular type. Examples of signal bearing media include, but are not limited to, a recordable type medium such as a flexible disk, a hard disk drive (HDD), a compact disk (CD), a digital versatile disk (DVD) ; And digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.).

The subject matter described herein sometimes illustrates different components that are included or linked in different different components. It should be understood that such depicted architectures are merely examples and that many other architectures that achieve substantially the same functionality can be implemented. In conceptual terms, any arrangement of components that achieve the same functionality is effectively "related " to achieve the desired functionality. Thus, any two components herein coupled to achieve a particular functionality may be viewed as being "associated " with each other so that the desired functionality is achieved regardless of architectures or intervening components. Likewise, any two components so associated may also be viewed as being "operably linked" or "operably coupled" to each other to achieve the desired functionality, and any two The two components may also be viewed as " operably coupleable "to one another to achieve the desired functionality. Specific examples of operably coupleable include, but are not limited to, components that are physically paired and / or physically interact and / or components that interact wirelessly and / or interact wirelessly and / ≪ / RTI > and / or logically interactable components.

For use herein of substantially any plural and / or singular terms, ordinary descriptors may be converted from plural to singular and / or singular to plural as appropriate to the context and / or application. Multiple singular / plural substitutions may be expressly stated herein for clarity.

In general, it will be understood by those of ordinary skill in the art that the terms used herein, and in particular in the appended claims (e.g., in the text of the appended claims), are generally intended to be "open" , The word "comprising" should be interpreted as "including but not limited to", and the term "having" should be interpreted as "having at least" and the term "comprising" Etc.). It will be understood by those skilled in the art that the intent is to be expressly set forth in the claims, if a particular number of the recited claims is intended, and that such intent is not without such statements. For example, as an aid to understanding, the following appended claims may include the use of the introductory phrases "at least one" and "one or more" The use of such phrases, however, is not intended to be exhaustive or to limit the scope of the present invention to the broader context of the present invention, (E.g., "a" and / or "an" should normally be interpreted to mean "at least one" or "one or more"), and the inclusion of such introduced claim entries And should not be construed to imply that the invention is limited to any claimed subject matter, including only one such claim; The same is true of the use of the definite articles used to introduce claim claims. It will also be appreciated by those skilled in the art that, even if a specific number of the claimed claims is explicitly recited, those skilled in the art will recognize that such description is usually construed to mean at least the stated number (e.g., Quot ;, usually means at least two descriptions, or two or more descriptions). Also, in those instances where a convention similar to "at least one of A, B, and C, etc." is used, such a configuration is generally intended in the sense of those skilled in the art to understand the convention (e.g., And C include systems having only A, B, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together In those cases where a convention similar to "at least one of A, B, and C" is used, such a configuration is generally intended in the sense that those skilled in the art understand the convention (eg, For example, a system having at least one of A, B, and C may be combined with A only, B only, C only, A and B together, A and C together, B and C together, and / or A, ≪ / RTI > and the like). Indeed any arbitrary disjunctive words and / or phrases that represent two or more alternative terms are intended to encompass possibilities to include any of the terms, either, either or both terms, irrespective of the description, the claims, As will be understood by those skilled in the art. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B".

Although certain example techniques have been described and illustrated herein using various methods and systems, it should be understood by those skilled in the art that various other modifications may be made without departing from the claimed subject matter, and equivalents may be substituted. In addition, many modifications may be made to adapt a particular situation to the teachings of the claimed subject matter without departing from the central concept set forth herein. It is therefore intended that the claimed subject matter is not limited to the specific examples disclosed, and that the claimed subject matter may also include all implementations falling within the scope of the appended claims and their equivalents.

Claims (31)

A method of providing an application programming interface testing service,
Determining a plurality of application programming interface calls used by a service in an origin data center;
Converting each of the plurality of application programming interface calls into a test segment to generate a plurality of test segments;
Forming an application programming interface test module for a plurality of target data centers, wherein the application programming interface test module comprises each of the plurality of test segments;
Transmitting the application programming interface test module from the origin data center to the target data center for execution on the plurality of target data centers over a communication network;
Receiving one or more test results based at least in part on the transmitted application programming interface test module executing on the plurality of target data centers; And
And generating a report based on the one or more test results indicating which of the application programming interface calls from the origin data center is compatible with the plurality of target data centers. How to. delete The method according to claim 1,
Further comprising receiving a test report comprising test results for each of the plurality of test segments based at least in part on the transmitted application programming interface test module executing on the plurality of target data centers, How to provide interface testing services. The method according to claim 1,
Receiving one or more test results based at least in part on sent application programming interface test modules executed in the plurality of target data centers, wherein the application programming interface test module receives a hypertext transfer protocol get request Wherein the one or more test results further comprises receiving the one or more test results, the indication including an indication that the hypertext transfer protocol get request was successful. The method according to claim 1,
Receiving one or more first test results based at least in part on the transmitted application programming interface test module executing on the plurality of target data centers;
Transmitting the application programming interface test module from the origin data center to the second plurality of target data centers for execution in a second plurality of target data centers over a communication network;
Receiving one or more second test results based at least in part on the transmitted application programming interface test module executing on the second plurality of target data centers; And
And comparing the one or more second test results to the one or more second test results. The method according to claim 1,
Wherein determining the plurality of application programming interface calls used by the service at the origin data center comprises:
Capturing a first in-operation network message at a network processor of the origin data center;
Extracting a first application programming interface call from the network message during the first operation; And
And including the first application programming interface call in the plurality of application programming interface calls. The method according to claim 1,
Wherein determining the plurality of application programming interface calls used by the service at the origin data center comprises:
Capturing a first simple object access protocol message at a network processor of the origin data center;
Extracting a first application programming interface call from the first simple object access protocol message; And
And including the first application programming interface call in the plurality of application programming interface calls. The method according to claim 1,
Wherein determining the plurality of application programming interface calls used by the service at the origin data center comprises:
Snooping network messages for application programming interface calls at a network processor of the origin data center to detect a first message having a first application programming interface call and a second message having a second application programming interface call;
Determining whether the first application programming interface call and the second application programming interface call are substantially similar; And
The method comprising: if the first application programming interface call and the second application programming interface call are substantially similar, including the first application programming interface call in the plurality of application programming interface calls How to. 9. The method of claim 8,
And discarding the second application programming interface call. ≪ Desc / Clms Page number 21 > The method according to claim 1,
The plurality of application programming interface calls may include a hypertext transfer protocol get request, a hypertext transfer protocol put request, a key-value save command, a messaging call, a queuing call, a remote save call, a delivery request to a content delivery network, And an administrative command to the content delivery network. ≪ Desc / Clms Page number 21 > The method according to claim 1,
Wherein the service at the origin data center comprises an in-use application. The method according to claim 1,
Wherein the plurality of test segments comprises an application programming interface setup call. The method according to claim 1,
Wherein the plurality of test segments comprises an application programming interface call in an error detection loop configured to record whether the application programming interface call correctly executed or returned an error. The method according to claim 1,
The plurality of test segments comprising an application programming interface call in an error detection loop configured to record whether the application programming interface call correctly executed or returned an error,
Wherein the error detection loop comprises at least one of a header or a footer. The method according to claim 1,
Wherein determining the plurality of application programming interface calls used by the service at the origin data center comprises:
Evaluating the code repository to detect code level application programming interface calls; And
And including the code level application programming interface call in the plurality of application programming interface calls. The method according to claim 1,
Wherein the application programming interface test module is configured to cycle through each of the plurality of test segments at the plurality of target data centers. A machine-readable non-volatile medium storing instructions,
Wherein the instructions, when executed, cause the device to:
Determining a plurality of application programming interface calls used by a service in an origin data center;
Converting each of the plurality of application programming interface calls into a test segment to generate a plurality of test segments;
Forming an application programming interface test module for a plurality of target data centers, wherein the application programming interface test module comprises each of the plurality of test segments;
Transmitting the application programming interface test module from the origin data center to the plurality of target data centers for execution on the plurality of target data centers via a communication network;
Receiving one or more test results based at least in part on the transmitted application programming interface test module executing on the plurality of target data centers; And
Generating a report based on the one or more test results indicating which of the application programming interface calls from the origin data center is compatible with the plurality of target data centers
To provide an application programming interface testing service. delete delete delete delete delete delete delete As a device,
When executed, cause the device to:
Determining a plurality of application programming interface calls used by a service in an origin data center;
Converting each of the plurality of application programming interface calls into a test segment to generate a plurality of test segments;
Forming an application programming interface test module for a plurality of target data centers, wherein the application programming interface test module comprises each of the plurality of test segments;
Transmitting the application programming interface test module from the origin data center to the plurality of target data centers for execution on the plurality of target data centers via a communication network;
Receiving one or more test results based at least in part on the transmitted application programming interface test module executing on the plurality of target data centers; And
Generating a report based on the one or more test results indicating which of the application programming interface calls from the origin data center is compatible with the plurality of target data centers
A machine readable medium having stored thereon instructions for providing an application programming interface testing service; And
And a processor coupled to the machine readable medium to execute the instructions. delete delete delete delete delete delete

Images