Scalable, distributed, fault-tolerant test framework

• US 9,720,818 B2
• Filed: 09/03/2015
• Issued: 08/01/2017
• Est. Priority Date: 09/03/2015
• Status: Active Grant

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: Edmonds, Michael David
• Primary Examiner(s): Khatri, Anil
• Application Number:
  US14/844,795
• Publication Number:
  US 20170068613A1
• Time in Patent Office: 698 Days
• Field of Search: 717123-129
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

A testing framework has been developed to address these issues that takes common functionality normally imported by the testing scripts on the client device and instead splits the functionality into standalone, fault tolerant, scalable services. Accordingly, the scripts can utilize the functionality through APIs and therefore test drivers executing a test or building a test environment or other testing processes may access the services through an API. Therefore, each testing client and test driver does not need to separately import the functionality and run the functionality on the memory of the client device separately. Rather, multiple tests can use these functionalities, allowing the testing services to be scaled between tests.

Claims

1. A method, comprising:

receiving, at a device from a first client device, a request for first functionality for performing a test of a storage controller,

wherein the first functionality comprises configuration functionality including processes for preparing a data structure on the storage controller to perform a failover test, wherein the preparing the data structure comprises copying a volume of data to create a new volume to be used for the failover test;

sending to the first client device an application programming interface (API) for the first functionality, wherein the API is populated with API functionality used to invoke performance of the failover test for the storage controller;

receiving, from the API that is at the first client device, a test request to perform the failover test to test the storage controller; and

executing the test request to perform the failover test by copying data from a first location to a new location as test data for use by the failover test and invoking the storage controller to perform a failover utilizing the test data.

2. The method of claim 1, wherein a test script is utilized for performing the failover test.

3. The method of claim 1, wherein the new volume is used as test data.

4. The method of claim 1, wherein the device receives a second request for the first functionality from a second client device.

5. The method of claim 4, wherein the device sends the API for the first functionality to the second client device.

6. A non-transitory machine readable medium having stored thereon instructions for performing a method, which when executed by machine, causes the machine to:

send, from a client device to a device, a request for a first service to perform a test, associated with first functionality, of a storage controller,

wherein the first functionality comprises configuration functionality including processes for preparing a data structure on the storage controller to perform a failover test, wherein the preparing the data structure comprises copying a volume of data to create a new volume to be used for the failover test;

import an application programming interface (API) for the first service from the device, wherein the API is populated with API functionality used to invoke performance of the failover test for the storage controller; and

sending a test request through the API to the device to request the first service to perform the failover test by copying data from a first location to a new location as test data for use by the failover test and invoke the storage controller to perform a failover utilizing the test data.

7. The method of claim 6, wherein a test script is utilized for performing the failover test.

8. The method of claim 6, wherein the new volume is used as test data.

9. The method of claim 8, wherein the client device imports a second API for a second functionality.

10. A computing device comprising:

a memory containing machine readable medium comprising machine executable code having stored thereon instructions for performing a method;

a processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to;

receive, from a first client device, a request for first functionality for performing a test of a storage controller,

wherein the first functionality comprises configuration functionality including processes for preparing a data structure on the storage controller to perform a failover test, wherein the preparing the data structure comprises copying a volume of data to create a new volume to be used for the failover test;

send to the first client device an application programming interface (API) for the first functionality, wherein the API is populated with API functionality used to invoke performance of the failover test for the storage controller;

receive, from the API that is at the first client device, a test request to perform the failover test to test the storage controller; and

execute the test request to perform the failover test by copying data from a first location to a new location as test data for use by the failover test and invoking the storage controller to perform a failover utilizing the test data.

11. The method of claim 10, wherein a test script is utilized for performing the failover test.

12. The method of claim 10, wherein the new volume is used as test data.

13. The method of claim 10, wherein the device receives a second request for the first functionality from a second client device.

14. The method of claim 13, wherein the device sends the API for the first functionality to the second client device.