Sign In to Follow Application
View All Documents & Correspondence

Systems And Methods For Improved Software Testing Project Execution

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.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
10 December 2013
Publication Number
51/2013
Publication Type
INA
Invention Field
COMPUTER SCIENCE
Status
Email
Parent Application
Patent Number
Legal Status
Grant Date
2023-06-07
Renewal Date

Applicants

WIPRO LIMITED
Doddakannelli, Sarjapur Road, Bangalore 560035, Karnataka, India.

Inventors

1. SOURAV SAM BHATTACHARYA
13418 N Cliff Top Drive, Fountain Hills, Arizona 85268, United States of America
2. ALKA GARG
9321 139th CT NE, Redmond, WA 98052, United States of America
3. ANOOP RAJAN RAJAN
3672 144th PL NE, APT N3, Bellevue, WA 98007, United States of America

Specification

CLIAMS:We claim
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.

Dated this 10th day of December, 2013
Sravan Kumar Gampa
Of K&S Partners
Agent for the Applicant
,TagSPECI:TECHNICAL FIELD
This disclosure relates generally to software development, and more particularly to systems and methods for improved software testing project execution.

Documents

Orders

Section Controller Decision Date

Application Documents

# Name Date
1 5679-CHE-2013 FORM-9 10-12-2013.pdf 2013-12-10
1 5679-CHE-2013-IntimationOfGrant07-06-2023.pdf 2023-06-07
2 5679-CHE-2013-PatentCertificate07-06-2023.pdf 2023-06-07
2 5679-CHE-2013 FORM-18 10-12-2013.pdf 2013-12-10
3 IP25633-spec.pdf 2013-12-12
3 5679-CHE-2013-FORM 3 [02-05-2023(online)].pdf 2023-05-02
4 IP25633-Drawings.pdf 2013-12-12
4 5679-CHE-2013-FORM-26 [02-05-2023(online)].pdf 2023-05-02
5 Form 5.pdf 2013-12-12
5 5679-CHE-2013-PETITION UNDER RULE 137 [02-05-2023(online)].pdf 2023-05-02
6 Form 3.pdf 2013-12-12
6 5679-CHE-2013-Written submissions and relevant documents [02-05-2023(online)].pdf 2023-05-02
7 5679-CHE-2013-FER.pdf 2019-09-02
7 5679-CHE-2013-AMENDED DOCUMENTS [03-04-2023(online)].pdf 2023-04-03
8 5679-CHE-2013-FORM 3 [02-03-2020(online)].pdf 2020-03-02
8 5679-CHE-2013-Correspondence to notify the Controller [03-04-2023(online)].pdf 2023-04-03
9 5679-CHE-2013-FORM 13 [03-04-2023(online)].pdf 2023-04-03
9 5679-CHE-2013-FER_SER_REPLY [02-03-2020(online)].pdf 2020-03-02
10 5679-CHE-2013-DRAWING [02-03-2020(online)].pdf 2020-03-02
10 5679-CHE-2013-POA [03-04-2023(online)].pdf 2023-04-03
11 5679-CHE-2013-CLAIMS [02-03-2020(online)].pdf 2020-03-02
11 5679-CHE-2013-US(14)-HearingNotice-(HearingDate-17-04-2023).pdf 2023-03-21
12 5679-CHE-2013-ABSTRACT [02-03-2020(online)].pdf 2020-03-02
13 5679-CHE-2013-CLAIMS [02-03-2020(online)].pdf 2020-03-02
13 5679-CHE-2013-US(14)-HearingNotice-(HearingDate-17-04-2023).pdf 2023-03-21
14 5679-CHE-2013-DRAWING [02-03-2020(online)].pdf 2020-03-02
14 5679-CHE-2013-POA [03-04-2023(online)].pdf 2023-04-03
15 5679-CHE-2013-FER_SER_REPLY [02-03-2020(online)].pdf 2020-03-02
15 5679-CHE-2013-FORM 13 [03-04-2023(online)].pdf 2023-04-03
16 5679-CHE-2013-Correspondence to notify the Controller [03-04-2023(online)].pdf 2023-04-03
16 5679-CHE-2013-FORM 3 [02-03-2020(online)].pdf 2020-03-02
17 5679-CHE-2013-AMENDED DOCUMENTS [03-04-2023(online)].pdf 2023-04-03
17 5679-CHE-2013-FER.pdf 2019-09-02
18 5679-CHE-2013-Written submissions and relevant documents [02-05-2023(online)].pdf 2023-05-02
18 Form 3.pdf 2013-12-12
19 5679-CHE-2013-PETITION UNDER RULE 137 [02-05-2023(online)].pdf 2023-05-02
19 Form 5.pdf 2013-12-12
20 IP25633-Drawings.pdf 2013-12-12
20 5679-CHE-2013-FORM-26 [02-05-2023(online)].pdf 2023-05-02
21 IP25633-spec.pdf 2013-12-12
21 5679-CHE-2013-FORM 3 [02-05-2023(online)].pdf 2023-05-02
22 5679-CHE-2013-PatentCertificate07-06-2023.pdf 2023-06-07
22 5679-CHE-2013 FORM-18 10-12-2013.pdf 2013-12-10
23 5679-CHE-2013-IntimationOfGrant07-06-2023.pdf 2023-06-07
23 5679-CHE-2013 FORM-9 10-12-2013.pdf 2013-12-10

Search Strategy

1 searchstrategy_02-07-2019.pdf

ERegister / Renewals

3rd: 02 Sep 2023

From 10/12/2015 - To 10/12/2016

4th: 02 Sep 2023

From 10/12/2016 - To 10/12/2017

5th: 02 Sep 2023

From 10/12/2017 - To 10/12/2018

6th: 02 Sep 2023

From 10/12/2018 - To 10/12/2019

7th: 02 Sep 2023

From 10/12/2019 - To 10/12/2020

8th: 02 Sep 2023

From 10/12/2020 - To 10/12/2021

9th: 02 Sep 2023

From 10/12/2021 - To 10/12/2022

10th: 02 Sep 2023

From 10/12/2022 - To 10/12/2023

11th: 02 Dec 2023

From 10/12/2023 - To 10/12/2024

12th: 02 Dec 2024

From 10/12/2024 - To 10/12/2025