Sign In to Follow Application
View All Documents & Correspondence

A Method And System For Testing Mobile Applications

Abstract: A method, corresponding system, and computer program product for testing mobile applications in a mobile application testing system is disclosed. The method includes creating at least one Docker container in the mobile application testing system. After creating the at least one docker container, the method identifies a mobile application for testing. The method automatically generates at least one test artifact in response to identifying the mobile application for testing. Thereafter, the method installs the at least one test artifact for the mobile application for testing in the at least one Docker container. Further, the method selects at least one mobile device in response to installing the at least one test artifact for the mobile application for testing in the at least one Docker container. Thereafter, the method executes the at least one test artifact for the at least one selected mobile device in the at least one Docker container. FIG. 2

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
28 September 2016
Publication Number
14/2018
Publication Type
INA
Invention Field
PHYSICS
Status
Email
ipo@knspartners.com
Parent Application
Patent Number
Legal Status
Grant Date
2023-11-22
Renewal Date

Applicants

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

Inventors

1. RAJKUMAR JOGHEE BHOJAN
#53, Daddy's Garden Layout, 1st Phase, 4th Cross, Hebbagodi, Bangalore 560 100, Karnataka, India.

Specification

Claims:WE CLAIMS
1. A method for testing mobile applications in a mobile application testing system, the method comprising:
creating, by a mobile application testing module, at least one Docker container in the mobile application testing system;
identifying, by the mobile application testing module, a mobile application for testing;
automatically generating, by the mobile application testing module; at least one test artifact in response to identifying the mobile application for testing;
installing, by the mobile application testing module, the at least one test artifact for the mobile application for testing in the at least one Docker container;
selecting, by the mobile application testing module, at least one mobile device in response to installing the at least one test artifact for the mobile application for testing in the at least one Docker container; and
executing, by the mobile application testing module, the at least one test artifact for the at least one selected mobile device in the at least one Docker container.
2. The method of claim 1 further comprising installing at least one of a mobile testing tool, a continuous integration tool, a test data management tool, and a mobile driver file in the at least one Docker container.
3. The method of claim 1, wherein identifying the mobile application for testing comprises receiving information associated with a user requirement from at least one of a software tool, and a user interface.
4. The method of claim 1, wherein automatically generating the at least one test artifact comprises:
creating at least one test case based on the mobile application for testing;
creating test data for the at least one created test case; and
generating a test script based on the at least one test case and the test data.
5. The method of claim 1, wherein selecting comprises using a machine learning algorithm for selecting the at least one mobile device.
6. The method of claim 1, wherein selecting comprises inputting the at least one mobile device by a user.
7. The method of claim 1, wherein executing the at least one test artifact comprises converting each docker container of the at least one docker container into an image file.
8. The method of claim 7, wherein executing the at least one test artifact further comprises deploying the image file for parallel execution in the at least one Docker container.
9. The method of claim 1 further comprising generating a test report in response to executing the at least one test artifact for the at least one selected mobile device in the at least one Docker container, wherein the test report comprises information associated with outcome of the execution of the at least one test artifact.
10. The method of claim 9 further comprising storing the generated test report in a database for future analysis.
11. A mobile application testing system for testing mobile applications, the system comprising:
a user interface;
a database; and
a mobile application testing module operatively coupled to the user interface and the database, the mobile application testing module configured to:
create at least one Docker container in the mobile application testing system;
identify a mobile application for testing;
automatically generate at least one test artifact in response to identifying the mobile application for testing;
install the at least one test artifact for the mobile application for testing in the at least one Docker container;
select at least one mobile device in response to installing the at least one test artifact for the mobile application for testing in the at least one Docker container; and
execute the at least one test artifact for the at least one selected mobile device in the at least one Docker container.

12. The mobile application testing system of claim 11, wherein the mobile application testing module is further configured to install at least one of a mobile testing tool, a continuous integration tool, a test data management tool, and a mobile driver file in the at least one Docker container.
13. The mobile application testing system of claim 11, wherein the mobile application testing module is further configured to receive information associated with a user requirement from at least one of a software tool, and the user interface.
14. The mobile application testing system of claim 11, wherein the mobile application testing module is further configured to:
create at least one test case based on the mobile application for testing;
create test data for the at least one created test case; and
generate a test script based on the at least one test case and the test data.
15. The mobile application testing system of claim 11, wherein the mobile application testing module is further configured to use a machine learning algorithm for selecting the at least one mobile device.
16. The mobile application testing system of claim 11, wherein the mobile application testing module is further configured to receive input about the at least one mobile device by a user.
17. The mobile application testing system of claim 11, wherein the mobile application testing module is further configured to convert each docker container of the at least one docker container into an image file.
18. The mobile application testing system of claim 17, wherein the mobile application testing module is further configured to deploy the image file in the at least one Docker container for parallel execution of the at least one test artifact.
19. The mobile application testing system of claim 11, wherein the mobile application testing module is further configured to generate a test report in response to executing the at least one test artifact for the at least one selected mobile device in the at least one Docker container, wherein the test report comprises information associated with outcome of the execution of the at least one test artifact.

20. The mobile application testing system of claim 11, wherein the mobile application testing module is further configured to store the generated test report in the database for future analysis.

Dated this 28th day of September, 2016

R Ramya Rao
Of K&S Partners
Agent for the Applicant
, Description:TECHNICAL FIELD
The disclosure relates generally to mobile applications and more particularly to methods and systems for testing mobile applications.

Documents

Application Documents

# Name Date
1 Form 5 [28-09-2016(online)].pdf 2016-09-28
2 Form 3 [28-09-2016(online)].pdf 2016-09-28
3 Form 18 [28-09-2016(online)].pdf_86.pdf 2016-09-28
4 Form 18 [28-09-2016(online)].pdf 2016-09-28
5 Drawing [28-09-2016(online)].pdf 2016-09-28
6 Description(Complete) [28-09-2016(online)].pdf 2016-09-28
7 REQUEST FOR CERTIFIED COPY [04-10-2016(online)].pdf 2016-10-04
8 Form 26 [04-10-2016(online)].pdf 2016-10-04
9 abstract 201641033196 .jpg 2016-11-04
10 Other Patent Document [17-11-2016(online)].pdf 2016-11-17
11 Correspondence By Agent_Form1 F30_21-11-2016.pdf 2016-11-21
12 REQUEST FOR CERTIFIED COPY [08-12-2016(online)].pdf 2016-12-08
13 Form 3 [26-12-2016(online)].pdf 2016-12-26
14 201641033196-FER.pdf 2019-10-23
15 201641033196-OTHERS [23-04-2020(online)].pdf 2020-04-23
16 201641033196-Information under section 8(2) [23-04-2020(online)].pdf 2020-04-23
17 201641033196-FORM 3 [23-04-2020(online)].pdf 2020-04-23
18 201641033196-FER_SER_REPLY [23-04-2020(online)].pdf 2020-04-23
19 201641033196-DRAWING [23-04-2020(online)].pdf 2020-04-23
20 201641033196-CORRESPONDENCE [23-04-2020(online)].pdf 2020-04-23
21 201641033196-COMPLETE SPECIFICATION [23-04-2020(online)].pdf 2020-04-23
22 201641033196-CLAIMS [23-04-2020(online)].pdf 2020-04-23
23 201641033196-ABSTRACT [23-04-2020(online)].pdf 2020-04-23
24 201641033196-PatentCertificate22-11-2023.pdf 2023-11-22
25 201641033196-IntimationOfGrant22-11-2023.pdf 2023-11-22
26 201641033196-PROOF OF ALTERATION [14-03-2024(online)].pdf 2024-03-14

Search Strategy

1 search_17-10-2019.pdf

ERegister / Renewals

3rd: 19 Feb 2024

From 28/09/2018 - To 28/09/2019

4th: 19 Feb 2024

From 28/09/2019 - To 28/09/2020

5th: 19 Feb 2024

From 28/09/2020 - To 28/09/2021

6th: 19 Feb 2024

From 28/09/2021 - To 28/09/2022

7th: 19 Feb 2024

From 28/09/2022 - To 28/09/2023

8th: 19 Feb 2024

From 28/09/2023 - To 28/09/2024

9th: 26 Sep 2024

From 28/09/2024 - To 28/09/2025

10th: 25 Sep 2025

From 28/09/2025 - To 28/09/2026