Sign In to Follow Application
View All Documents & Correspondence

System And Method For Optimizing Testing Of Software Production Incidents

Abstract: This disclosure relates generally to software testing, and more particularly to a system and method for optimizing testing of software production incidents. In one embodiment, the method comprises analyzing an incident ticket using a machine learning algorithm to identify one or more keywords in the incident ticket, and identifying a location of the incident ticket based on the one or more keywords, a test workspace corresponding to the incident ticket based on the location, and a plurality of specific test cases corresponding to the incident ticket based on the test workspace. The identification leads to a first scenario and a second scenario. In the first scenario, the method further comprises initiating a learning process based on intelligence gathered from a manual processing of the incident ticket. In the second scenario, the method further comprises executing the plurality of specific test cases in a test environment. Figure 3

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
03 September 2015
Publication Number
37/2015
Publication Type
INA
Invention Field
COMPUTER SCIENCE
Status
Email
ipr@akshipassociates.com
Parent Application

Applicants

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

Inventors

1. VENKATA SUBRAMANIAN JAYARAMAN
41, Venkateswara Colony, 10th Street, M.M.C, Chennai - 600 051, Tamil Nadu, India.
2. RAJIV KUMAR AGRAWAL
101 Aster, Manar Silver Shadows, Kaikondrahalli, Sarjapur Road, Bangalore, Karnataka, India.
3. GANESH NARAYAN
51, 2nd Stage, Karnataka Layout, Basaveshwaranagar PO., Bangalore - 560079, Karnataka, India.
4. BHARATH KUMAR HEMACHANDRAN
Oak 705 SJR Park Vista, Haralur Road, Off Sarjapur Road, Bangalore - 560102, Karnataka, India.

Specification

Claims:WE CLAIM:
1. A method for optimizing testing of software production incidents, the method comprising:
categorizing, via a processor, an incident ticket received from one or more sources based on one or more pre-defined parameters, the incident ticket corresponding to an obstruction in a software production;
in response to categorization, analyzing, via the processor, the incident ticket using a machine learning algorithm to identify one or more keywords in the incident ticket;
identifying, via the processor, a location of the incident ticket based on the one or more keywords, a test workspace corresponding to the incident ticket based on the location, and a plurality of specific test cases corresponding to the incident ticket based on the test workspace, the identification leading to a first scenario and a second scenario;
in the first scenario, initiating, via the processor, a learning process based on intelligence gathered from a manual processing of the incident ticket; and
in the second scenario,
identifying, via the processor, a test environment for the plurality of specific test cases; and
executing, via the processor, the plurality of specific test cases in the test environment.

2. The method of claim 1, further comprising logging the incident ticket in an incident repository.

3. The method of claim 1, wherein the one or more predefined parameters comprise at least one of a person, a system, and a location related to the incident ticket.

4. The method of claim 1, wherein identifying the location of the incident ticket comprises referring to a keyword-location mapping.

5. The method of claim 1, further comprising routing the incident ticket to the identified location based on at least one of a priority and a severity rating of the one or more keywords and the identified location.

6. The method of claim 1, wherein identifying the test workspace corresponding to the incident ticket comprises referring to a location-workspace mapping.

7. The method of claim 1, wherein identifying the plurality of specific test cases comprises:
identifying a test case location from a plurality of test workspaces by referring to a location-workspace mapping and a search keyword mapping; and
identifying the plurality of specific test cases from the test case location.

8. The method of claim 1, wherein identifying the plurality of specific test cases comprises analyzing a plurality of test cases in the test workspace based on the one or more keywords using the machine learning algorithm.

9. The method of claim 1, further comprising verifying the plurality of specific test cases for suitability to testing of the incident ticket.

10. The method of claim 1, wherein the first scenario corresponds to a negative identification of at least one of the location, the test workspace, and the plurality of specific test cases, and wherein the second scenario corresponds to a positive identification of the location, the test workspace, and the plurality of specific test cases.

11. The method of claim 1, wherein identifying the test environment comprises preparing the test environment corresponding to an environment of the software production and based on the plurality of specific test cases.

12. The method of claim 1, wherein the incident ticket resulting in the first scenario comprises a new incident ticket unrelated to a plurality of past incident tickets and not having at least one of a corresponding location, a corresponding test workspace, and a corresponding specific test case, and wherein the manual processing of the new incident ticket comprises generating at least one of a solution, a location, a test workspace, a test case, and a test environment.

13. The method of claim 1, further comprising updating at least one of a location repository, a test workspace repository, a test case repository, a keyword-location mapping, a location-workspace mapping, and a search keyword mapping based on the learning process.

14. The method of claim 1, further comprising generating a report indicating at least one of a result of the execution, a cause leading to failure of the execution, an effectiveness of implementation of the optimized testing, an area with high number of incident tickets that require implementation of the optimized testing, and a return on investment analysis related to implementation of the optimized testing.

15. A system for optimizing testing of software production incidents, the system comprising:
at least one processor; and
a computer-readable medium storing instructions that, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
categorizing an incident ticket received from one or more sources based on one or more pre-defined parameters, the incident ticket corresponding to an obstruction in a software production;
in response to categorization, analyzing the incident ticket using a machine learning algorithm to identify one or more keywords in the incident ticket;
identifying a location of the incident ticket based on the one or more keywords, a test workspace corresponding to the incident ticket based on the location, and a plurality of specific test cases corresponding to the incident ticket based on the test workspace, the identification leading to a first scenario and a second scenario;
in the first scenario, initiating a learning process based on intelligence gathered from a manual processing of the incident ticket; and
in the second scenario, identifying a test environment for the plurality of specific test cases, and executing the plurality of specific test cases in the test environment.

16. The system of claim 15, wherein identifying the location of the incident ticket comprises referring to a keyword-location mapping, and wherein identifying the test workspace corresponding to the incident ticket comprises referring to a location-workspace mapping, and wherein identifying the plurality of specific test cases comprises identifying a test case location from a plurality of test workspaces by referring to a location-workspace mapping and a search keyword mapping and identifying the plurality of specific test cases from the test case location.

17. The system of claim 15, wherein the first scenario corresponds to a negative identification of at least one of the location, the test workspace, and the plurality of specific test cases, and wherein the second scenario corresponds to a positive identification of the location, the test workspace, and the plurality of specific test cases.

18. The system of claim 15, wherein the manual processing of the incident ticket comprises generating at least one of a solution, a location, a test workspace, a test case, and a test environment, and wherein the operations further comprise updating at least one of a location repository, a test workspace repository, a test case repository, a keyword-location mapping, a location-workspace mapping, and a search keyword mapping based on the learning process.

19. A non-transitory computer-readable medium storing computer-executable instructions for:
categorizing an incident ticket received from one or more sources based on one or more pre-defined parameters, the incident ticket corresponding to an obstruction in a software production;
in response to categorization, analyzing the incident ticket using a machine learning algorithm to identify one or more keywords in the incident ticket;
identifying a location of the incident ticket based on the one or more keywords, a test workspace corresponding to the incident ticket based on the location, and a plurality of specific test cases corresponding to the incident ticket based on the test workspace, the identification leading to a first scenario and a second scenario;
in the first scenario, initiating a learning process based on intelligence gathered from a manual processing of the incident ticket; and
in the second scenario, identifying a test environment for the plurality of specific test cases, and executing the plurality of specific test cases in the test environment.
Dated these on 3rd day of September, 2015

SWETHA SN OF K& S PARTNERS
AGENT FOR THE APPLICANT
, Description:TECHNICAL FIELD
This disclosure relates generally to software testing, and more particularly to a system and method for optimizing testing of software production incidents.

Documents

Orders

Section Controller Decision Date

Application Documents

# Name Date
1 4673-CHE-2015-Written submissions and relevant documents [25-11-2022(online)].pdf 2022-11-25
1 Form 9 [03-09-2015(online)].pdf 2015-09-03
2 4673-CHE-2015-US(14)-ExtendedHearingNotice-(HearingDate-11-11-2022).pdf 2022-11-04
2 Form 5 [03-09-2015(online)].pdf 2015-09-03
3 Form 3 [03-09-2015(online)].pdf 2015-09-03
3 4673-CHE-2015-AMENDED DOCUMENTS [01-11-2022(online)].pdf 2022-11-01
4 Form 18 [03-09-2015(online)].pdf 2015-09-03
4 4673-CHE-2015-Correspondence to notify the Controller [01-11-2022(online)].pdf 2022-11-01
5 Drawing [03-09-2015(online)].pdf 2015-09-03
5 4673-CHE-2015-FORM 13 [01-11-2022(online)].pdf 2022-11-01
6 Description(Complete) [03-09-2015(online)].pdf 2015-09-03
6 4673-CHE-2015-POA [01-11-2022(online)].pdf 2022-11-01
7 REQUEST FOR CERTIFIED COPY [04-09-2015(online)].pdf 2015-09-04
7 4673-CHE-2015-US(14)-HearingNotice-(HearingDate-07-11-2022).pdf 2022-10-19
8 abstract 4673-CHE-2015.jpg 2015-09-05
8 4673-CHE-2015-FER_SER_REPLY [29-07-2020(online)].pdf 2020-07-29
9 4673-CHE-2015-FORM 3 [29-07-2020(online)].pdf 2020-07-29
9 REQUEST FOR CERTIFIED COPY [21-12-2015(online)].pdf 2015-12-21
10 4673-CHE-2015-Information under section 8(2) [29-07-2020(online)].pdf 2020-07-29
10 4673-CHE-2015-Power of Attorney-180216.pdf 2016-06-30
11 4673-CHE-2015-Form 1-180216.pdf 2016-06-30
11 4673-CHE-2015-PETITION UNDER RULE 137 [29-07-2020(online)].pdf 2020-07-29
12 4673-CHE-2015-Correspondence-F1-PA-180216.pdf 2016-06-30
12 4673-CHE-2015-FER.pdf 2020-01-29
13 4673-CHE-2015-Correspondence-F1-PA-180216.pdf 2016-06-30
13 4673-CHE-2015-FER.pdf 2020-01-29
14 4673-CHE-2015-Form 1-180216.pdf 2016-06-30
14 4673-CHE-2015-PETITION UNDER RULE 137 [29-07-2020(online)].pdf 2020-07-29
15 4673-CHE-2015-Information under section 8(2) [29-07-2020(online)].pdf 2020-07-29
15 4673-CHE-2015-Power of Attorney-180216.pdf 2016-06-30
16 4673-CHE-2015-FORM 3 [29-07-2020(online)].pdf 2020-07-29
16 REQUEST FOR CERTIFIED COPY [21-12-2015(online)].pdf 2015-12-21
17 abstract 4673-CHE-2015.jpg 2015-09-05
17 4673-CHE-2015-FER_SER_REPLY [29-07-2020(online)].pdf 2020-07-29
18 REQUEST FOR CERTIFIED COPY [04-09-2015(online)].pdf 2015-09-04
18 4673-CHE-2015-US(14)-HearingNotice-(HearingDate-07-11-2022).pdf 2022-10-19
19 Description(Complete) [03-09-2015(online)].pdf 2015-09-03
19 4673-CHE-2015-POA [01-11-2022(online)].pdf 2022-11-01
20 Drawing [03-09-2015(online)].pdf 2015-09-03
20 4673-CHE-2015-FORM 13 [01-11-2022(online)].pdf 2022-11-01
21 Form 18 [03-09-2015(online)].pdf 2015-09-03
21 4673-CHE-2015-Correspondence to notify the Controller [01-11-2022(online)].pdf 2022-11-01
22 Form 3 [03-09-2015(online)].pdf 2015-09-03
22 4673-CHE-2015-AMENDED DOCUMENTS [01-11-2022(online)].pdf 2022-11-01
23 Form 5 [03-09-2015(online)].pdf 2015-09-03
23 4673-CHE-2015-US(14)-ExtendedHearingNotice-(HearingDate-11-11-2022).pdf 2022-11-04
24 Form 9 [03-09-2015(online)].pdf 2015-09-03
24 4673-CHE-2015-Written submissions and relevant documents [25-11-2022(online)].pdf 2022-11-25

Search Strategy

1 search10AE_10-03-2021.pdf
1 serach43(2)_19-12-2019.pdf
2 search43(1)_19-12-2019.pdf
3 search10AE_10-03-2021.pdf
3 serach43(2)_19-12-2019.pdf