SYSTEMS AND METHODS FOR IMPROVED SOFTWARE TESTING PROJECT EXECUTION

• US 20150113331A1
• Filed: 10/17/2013
• Published: 04/23/2015
• Est. Priority Date: 10/17/2013
• Status: Abandoned Application

• Current Assignee: Wipro Limited
• Original Assignee: Wipro Limited
• Inventors: Bhattacharya, Sourav Sam, Garg, Alka, Rajan, Anoop Rajan
• Application Number:
  US14/056,932
• Publication Number:
  US 20150113331A1
• Time in Patent Office: Days
• US Class Current: 714/38.1
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

This disclosure relates generally to software development, and more particularly to systems and methods for improved software testing project execution. In one embodiment, a software testing system is disclosed, comprising: a processor; and a memory storing processor-executable instructions comprising instructions for: obtaining a software test execution request including one or more software test cases to execute; identifying one or more software test environmental parameters; determining one or more computing systems for performing software test execution, based on the one or more software test environmental parameters; generating one or more configuration settings associated with initiating or terminating software test execution on the one or more computing systems; and storing the one or more configuration settings.

Claims

1. A software testing system, comprising:

a processor; and

a memory storing processor-executable instructions comprising instructions for;

obtaining a software test execution request including one or more software test cases to execute;

identifying one or more software test environmental parameters;

determining one or more computing systems for performing software test execution, based on the one or more software test environmental parameters;

generating one or more configuration settings associated with initiating or terminating software test execution on the one or more computing systems; and

storing the one or more configuration settings.

2. The system of claim 1, wherein the one or more software test environmental parameters includes at least one of:

a geographic location of one or more computing systems;

a time zone of one or more computing systems;

a labor availability parameter;

an energy price parameter;

or a labor cost parameter.

3. The system of claim 1, the instructions further comprising instructions for:

providing a notification with a recommended number of job sites to execute the test project, and furthermore providing a notification to at least one of the one or more computing systems to initiate software test execution, based on at least one of the stored configuration settings.

4. The system of claim 3, wherein the software test execution is configured for performing a functional test combined with a plurality of non-functional tests, including at least one of:

a security test;

or a performance test.

5. The system of claim 3, the instructions further comprising instructions for:

monitoring progress of the software test execution;

identifying a failover condition based on monitoring the progress of the software test execution;

terminating automatically the software test execution and initiating a next software test execution from a batch;

generating a report based on identifying the failover condition; and

storing the generated report.

6. The system of claim 5, wherein monitoring progress of the software test execution is performed by a standalone utility executed by the processor.

7. The system of claim 1, wherein at least one of the one or more configuration settings includes a calendar data object configured for alerting a user.

8. The system of claim 3, the instructions further comprising instructions for:

providing a notification of a storage location of a test script associated with the software test execution; and

providing a notification of a result of a batch-processed test script being uploaded to a test results database.

9. A software testing method, comprising:

obtaining a software test execution request including one or more software test cases to execute;

identifying one or more software test environmental parameters;

determining one or more computing systems for performing software test execution, based on the one or more software test environmental parameters;

generating one or more configuration settings associated with initiating or terminating software test execution on the one or more computing systems; and

storing the one or more configuration settings.

10. The method of claim 9, wherein the one or more software test environmental parameters includes at least one of:

a geographic location of one or more computing systems;

a time zone of one or more computing systems;

a labor availability parameter;

an energy price parameter;

or a labor cost parameter.

11. The method of claim 9, further comprising:

providing a notification with a recommended number of job sites to execute the test project, and furthermore providing a notification to at least one of the one or more computing systems to initiate software test execution, based on at least one of the stored configuration settings.

12. The method of claim 11, wherein the software test execution is configured for performing a functional test combined with a plurality of non-functional tests, including at least one of:

a security test;

or a performance test.

13. The method of claim 11, further comprising:

monitoring progress of the software test execution;

identifying a failover condition based on monitoring the progress of the software test execution;

terminating automatically the software test execution and initiating a next software test execution from a batch;

generating a report based on identifying the failover condition; and

storing the generated report.

14. The method of claim 13, wherein monitoring progress of the software test execution is performed by a standalone utility executed by the processor.

15. The method of claim 9, wherein at least one of the one or more configuration settings includes a calendar data object configured for alerting a user.

16. The method of claim 11, further comprising:

providing a notification of a storage location of a test script associated with the software test execution; and

providing a notification of a result of a batch-processed test script being uploaded to a test results database.

17. A non-transitory computer-readable medium storing computer-executable software testing instructions comprising instructions for:

obtaining a software test execution request including one or more software test cases to execute;

identifying one or more software test environmental parameters;

determining one or more computing systems for performing software test execution, based on the one or more software test environmental parameters;

generating one or more configuration settings associated with initiating or terminating software test execution on the one or more computing systems; and

storing the one or more configuration settings.

18. The medium of claim 17, wherein the one or more software test environmental parameters includes at least one of:

a geographic location of one or more computing systems;

a time zone of one or more computing systems;

a labor availability parameter;

an energy price parameter;

or a labor cost parameter.

19. The medium of claim 17, the instructions further comprising instructions for:

providing a notification with a recommended number of job sites to execute the test project, and furthermore providing a notification to at least one of the one or more computing systems to initiate software test execution, based on at least one of the stored configuration settings.

20. The medium of claim 19, wherein the software test execution is configured for performing a functional test combined with a plurality of non-functional tests, including at least one of:

a security test;

or a performance test.

21. The medium of claim 19, the instructions further comprising instructions for:

monitoring progress of the software test execution;

identifying a failover condition based on monitoring the progress of the software test execution;

terminating automatically the software test execution and initiating a next software test execution from a batch;

generating a report based on identifying the failover condition; and

storing the generated report.

22. The medium of claim 21, wherein monitoring progress of the software test execution is performed by a standalone utility executed by the processor.

23. The medium of claim 17, wherein at least one of the one or more configuration settings includes a calendar data object configured for alerting a user.

24. The medium of claim 19, the instructions further comprising instructions for:

providing a notification of a storage location of a test script associated with the software test execution; and

providing a notification of a result of a batch-processed test script being uploaded to a test results database.