Scalable, distributed, fault-tolerant test framework

US9720818B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9720818-B2
Application numberUS-201514844795-A
CountryUS
Kind codeB2
Filing dateSep 3, 2015
Priority dateSep 3, 2015
Publication dateAug 1, 2017
Grant dateAug 1, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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.

First claim

Opening claim text (preview).

The invention claimed is: 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.

Assignees

Inventors

Classifications

  • for test execution, e.g. scheduling of test suites · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9720818B2 cover?
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…
Who is the assignee on this patent?
Netapp Inc
What technology area does this patent fall under?
Primary CPC classification G06F11/3688. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Aug 01 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).