FORM 2
THE PATENTS ACT, 1970
(39 of 1970) , &
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
(See section 10, rule 13)
1. Title of the invention: AUTOMATED TESTING OF SOCIAL MEDIA APPLICATIONS
2. Applicant(s)
NAME NATIONALITY ADDRESS
TATA CONSULTANCY Indian Nirmal Building, 9th Floor,
SERVICES LIMITED Nariman Point, Mumbai,
| Maharashtra 400021, India
3. Preamble to the description
COMPLETE SPECIFICATION
The following specification particularly describes the invention and the manner in which it
is to be performed.

TECHNICAL FIELD
[0001] The present subject matter, in general, relates to software testing automation,
and in particular, to systems and methods for automated testing of social media applications.
BACKGROUND
[0002] Software testing is an important phase of the software development process.
Software testing is the process of interacting with software with the aim of revealing errors. Software testing is necessary in order to ensure that the software actually performs what it is supposed to do and does so correctly. The complete software testing process, generally referred to as testing lifecycle, includes a series of testing activities that may be iterative in nature. In the recent years, various social media applications related to advertisement, sales, and marketing have been developed. One example of such social media applications include a sales force application that allows people to connect to various companies/manufacturers and find about their products and/or services. Such social media applications are developed to meet various business requirements are required to be tested to determine their behavior. Based on the tested behavior, such social media applications are modified, and the modified applications are retested. With an increase in complexity of such social media applications as well as stringent quality requirements to be fulfilled by such applications, the demand for effective testing of such applications has increased.
SUMMARY
[0003] This summary is provided to introduce concepts related to an automated testing
of social media applications. These concepts are further described below in the detailed description. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining or limiting the scope of the claimed subject matter.
[0004] In one embodiment, a method for automated testing of a social media
application comprises receiving a process workflow diagram, which is created based on the business requirements associated with the social media application. The process workflow diagram is indicative of transfer of data and tasks through a work process for a service.

Further, the method may include generating a plurality of test scenarios based on the process workflow diagram. The method may also include generating a plurality of test cases for at least one test scenario amongst the plurality of test scenarios. In addition, the method may include generating a plurality of test scripts for the plurality of test bases. The plurality of test scripts is then executed to test the social media application.
BRIEF DESCRIPTION OF THE DRAWINGS
[0005] The detailed description is described with reference to the accompanying
figure(s). In the figure(s), the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figure(s) to reference like features and components.
[0006] Fig. 1(a) illustrates an automated testing system, in accordance with an
embodiment of the present subject matter.
[0007] Fig. 1(b) illustrates a block diagram of the automated testing system, in
accordance with an embodiment of the present subject matter.
[0008] Fig. 1(c) illustrates an exemplary process workflow diagram, in accordance
with an embodiment of the present subject matter.
[0009] Fig. 1(d) illustrates a set of exemplary test scenarios generated by the
automated testing system, in accordance with an embodiment of the present subject matter.
[0010] Fig. 1(e) illustrates a set of exemplary test cases generated by the automated
testing system, in accordance with an embodiment of the present subject matter.
[0011] Fig. 2 illustrates a method for an automated testing of a social media
application, in accordance with an embodiment of the present subject matter.
DETAILED DESCRIPTION
[0012] Process of testing social media applications typically involves a series of
phases, such as test planning, test designing, test execution, and test re-execution. Conventionally, several approaches have been followed to automate one or more of the phases or activities in the testing process. Owing to complexity of the social media

applications there is no single conventional tool that provides end-to-end automated testing of social media applications.
[0013] In accordance with the present subject matter, systems and methods for an
automated testing of social media applications, such as a sales force application is described. The systems and the methods enable the automatic generation of test scenarios from a process workflow diagram depicting the workflow of the social media application and associated business requirements. Based on the test scenarios, a plurality of test cases is generated and uploaded into a test management system, from where they are picked up and automatically converted into test scripts that can be executed, based on test data, to test the social media application. Test results obtained as a result of the testing are automatically saved into the test management system.
[0014] The systems and the methods of the present subject matter, thus, provides end
to end automated testing of the social media applications including automated generation of test scenarios, test cases, test scripts and its execution saves considerable time and efforts of the user. Further, automatic storing and logging of the generated test scenarios, test cases, test scripts, and test results obtained upon execution of each script, enables versioning and tracking of changes in business requirements or process workflow. Since the testing artifacts, such as test scenarios, test cases, and test scripts are stored in the test management system, the testing artifacts that are required for retesting of the social media application can be automatically picked up to carry out retesting of the social media application, if required.
[0015] The manner in which the automated testing of social media applications takes
place shall be explained in detail with respect to the Figs. 1-2. While aspects of systems and methods can be implemented in any number of different computing systems environments, and/or configurations, the embodiments are described in the context of the following exemplary system architecture(s). Furthermore, the present description has been provided with implementations that are specific to certain business functions or certain businesses. It would be appreciated that other implementations are also covered without deviating from the scope of the present subject matter.
[0016] Fig. 1(a) illustrates an automated testing system 100 (hereinafter referred to as
a testing system 100), according to an embodiment of the present subject matter. The testing

system 100 can be implemented in systems that include, but are not limited to, desktop computers, multiprocessor systems, laptops, network computers, cloud servers, minicomputers, mainframe computers, and the like.
[0017] In said embodiment, the testing system 100 includes one or more processor(s)
102, interface(s) 104, and a memory 106 coupled to the processor 102. The processor 102 can be a single processing unit or a number of units, all of which could also include multiple computing units. Among other capabilities, the processor 102 is configured to fetch and execute computer-readable instructions and data stored in the memory 106.
[0018] The interfaces 104 may include a variety of software and hardware interfaces,
for example, interface for peripheral device(s), such as a keyboard, a mouse, an external memory, and a printer. Further, the interfaces 104 may enable the testing system 100 to communicate with other computing devices, such as web servers, and external data repositories.
[0019] The memory 106 may include any non-transitory computer-readable medium
known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. The non-transitory computer-readable medium, however, excludes a transitory, propagating signal.
[0020] The testing system 100 further includes modules 108 and data 110. The
module(s) 108 include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement particular abstract data types. In one implementation, the module(s) 108 includes a process modeler 112, a test scenario and test case generator 114, a test script generator 116, a script executor 118, a test data generator 120, and other module(s) 122. The other module(s) 122 may include programs or coded instructions that supplement applications and functions of the testing system 100. The testing system 100 may be connected to a test management system 126. Although the test management system 126 is shown as a separate system, in the Fig.l (a), it may be understood that the test management system 126 can be integrated within the testing system 100, in another embodiment.

[0021] On the other hand, the data 110, inter alia serves as a repository for storing data
processed, received, and generated by one or more of the module(s) 108. The data 110 includes, for example, a process workflow diagram 128, test data 130, and other data 132. The other data 132 includes data generated as a result of the execution of one or more modules in the module(s) 108. Although the data 110 is shown internal to the testing system 100, it may be understood that the data 110 can reside in an external repository (not shown in the figure), which may be coupled to the testing system 100. The testing system 100 may communicate with the external repository through the interface(s) 104 to obtain information from the data 110.
[0022] In one embodiment, the modules 108 of the testing system 100 are capable of being implemented as separate systems, at disparate geographical locations and communicatively coupled through a network. The network may be a wireless network, a wired network, or a combination thereof. The network can also be an individual network or a collection of many such individual networks, interconnected with each other and functioning as a single large network, e.g., the Internet or an intranet. The network can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and such.
[0023] In one implementation, the testing system 100 may be implemented in a network environment. The network environment can be a company network, including thousands of office personal computers, laptops, various servers, such as blade servers, and other computing devices connected over the network. In another implementation, the network environment can be a home network with a limited number of personal computers and laptops connected over the network.
[0024] As mentioned herein, the present subject matter discloses a system and a
method for automated testing of social media applications. In one implementation, the testing system 100 may receive business requirements in the form of a process workflow diagram 128, such as a business process workflow diagram 128. A process workflow diagram 128 visually represents movement and transfer of resources, documents, data and tasks through the entire work process for a given product or service. A flowchart may represent the correct workflow quickly and clearly.

[0025] In one implementation, the process workflow diagram 128 is created using the
process modeler 112. The process modeler 112 described herein is a conventional workflow modeling tool integrated within the testing system 100. The process modeler 112 provides an interface to a user for creation of the process workflow diagram 128 based on the business requirements. In another implementation, the process workflow diagram 128 may be imported into the testing system 100 from various external sources. For example, the user may import pre-existing process workflow diagram 128 or create a process workflow diagram 128 using conventionally available modeling tools and provide such process workflow diagram 128 as input to the testing system 100. The process workflow diagram 128 may be a state transition diagram or a Unified Modeling Language (UML) activity diagram. In one implementation, the process modeler 112 may store the process workflow diagram 128 as the process workflow diagram 128 in the data 110.
[0026] The process workflow diagram 128 is received as an input by the test scenario
and test case generator 114. Upon receiving, the test scenario and test case generator 114 may determine all paths in the process workflow diagram 128 from a start state to an end state. A path may be understood as a series of actions that are performed when moving from one state to another state in the process workflow diagram 128. Such series of actions corresponds to a test scenario. Thus, a plurality of test scenarios are automatically generated covering each path in the process workflow diagram 128 from the start state to the end state.
[0027] In one implementation, subsequent to generation of the test scenarios, the test
scenario and test case generator 114 eliminates duplicated scenarios from the generated test scenarios, if any, to optimize the test scenarios. The duplicated scenarios may be understood as the test scenarios that are covered within one or more other test scenarios. Once the test scenarios are generated, the test scenario and test case generator 114 generates a plurality of test cases for the test scenarios. For generating the test cases, the test scenario and test case generator 114 performs pair-wise testing for each of the states (also referred to as parameters) in the test scenarios. In the pair-wise testing, for each pair of parameters in the test scenarios, the test scenario and test case generator 114 creates multiple pair-wise test sets that correspond to the plurality of test cases, for every combination of valid values of the parameters. Further, the test scenario and test case generator 114 may also test all possible

discrete combinations of the parameters. Accordingly, the pair-wise testing may catch potential bugs that may be present when specific pairs of items cause an issue.
[0028] The test scenario and test case generator 114, in one implementation, eliminates
the duplicated test cases or pair-wise test sets from the plurality of test cases to optimize the test cases. In one implementation, the test cases are generated for each of the test scenarios. In another implementation, the test cases are generated for the test scenarios selected by a user, such as a tester. Examples of the test scenario and test case generator 114 include a TCS Fusion tool.
[0029] The test scenarios and the test cases, thus, generated are uploaded or stored
into the test management system 126 by the test scenario and test case generator 114. The test scenarios are stored as test scenarios 134 and the test cases are stored as test cases 136 within the test management system 126.
[0030] In an implementation, the test management system 126 maintains data stored
therein. Examples of the test management system 126 may include, but are not limited to, TCS test management tool. The test management system 126 may facilitate management of various tests and data related to various stages of testing. When a social media application is to be tested, the test management system 126 invokes the test script generator 116 to convert the test cases into executable test scripts. Accordingly, the test script generator 116 may retrieve the test cases from the test management system 126 to generate test scripts for the test cases. In an implementation, the test script generator 116 is a script generation tool, such as TCS Reusable Automated Framework for Testing (RAFT). The test script generator 116 may generate the test scripts that may be selected.by the user based on, among other things, the social media application under testing. The generated test scripts are uploaded into the test management system 126 as test scripts 138.
[0031] The test management system 126 then invokes the script executor 118 to
execute the test scripts to test the social media application. Further, results of the execution are uploaded in the test management system 126 as test results 140. If the test results meet expectations, the social media application may be deployed. While, if the test results are unsatisfactory, the social media application may be modified by the development team and retested till expected results are obtained.

[0032] In one implementation, the test management system 126 may schedule an
automated execution of the tests by the script executor 118. In another implementation, execution of the test scripts may be triggered by the user. In one implementation, the test data generator 120-may provide the test data 130 that may be needed to execute the test scripts. In one implementation, the test data generator 120 may be associated with or integrated within the script executor 118 to provide the test data 130 upon which automated test scripts are executed. In another implementation, the test data 130 for testing the social media application may be provided by the user, such as a tester. The results of the testing may be stored in the test management system 126 for tracking and reference.
[0033] Thus, the testing system 100 may enable automatic generation of test scenarios
from a business process workflow diagram 128. These test scenarios may get automatically saved in a test management system 126 from where the test scenarios are picked up and automatically converted into test scripts for testing the social media application under testing. The test scripts are then executed, based on test data, to test the social media application, and the results generated gets saved automatically in the test management system 126. Thus, testing resources, i.e., time and efforts of a testing analyst, involved in designing test scenarios, test cases, and test scripts is significantly reduced, as the test analyst may not spend much time in managing the test scenarios, test cases, and test scripts.
[0034] It is to be understood that the specific tools referred above are only for the
purpose of examples. The same should not be constructed as a limitation. Any other tools with the same functionality may be used to serve the same purpose, without departing from the scope of the invention.
[0035] Fig 1(b) illustrates a block diagram of the testing system 100, in accordance
with an embodiment of the present subject matter. In said embodiment, the testing system 100 includes various modules, namely, the process modeler 112, the test scenario and test case generator 114, the test script generator 116, the script executor 118, and the test data generator 120. These modules may include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement particular abstract data types. For example, implemented as any of a variety of conventional computing devices, including, for example, servers, a desktop PC, a notebook or portable computer, a workstation, a mainframe

computer, a mobile computing device, and an internet appliance. In said embodiment, the test management system 126 is integrated within the testing system 100 as a module. Fig. 1(b) illustrates interaction of these modules for automated testing of the social media application.
[0036] It will be appreciated by one skilled in the art that these modules collectively
form the testing system 100. In other words, the testing system 100 is an integration of the various modules. The order in which the modules are arranged is not intended to be construed as a limitation, and any number of the modules can be combined in any order to implement the testing system 100 or an alternate testing system 100. Additionally, individual modules may be added or deleted from the testing system 100 without departing from the spirit and scope of the subject matter described herein. In one embodiment, the modules of the testing system 100 are capable of being implemented as separate systems, at disparate geographical locations and communicatively coupled through a network.
[0037] In operation, the process modeler 112 may be used to create or draw a process
workflow diagram 128 based on the business requirements associated with a social media application. In one example, the process workflow diagram 128 may be a state transition diagram. The process workflow diagram 128, thus, created is received as an input by the test scenario and test case generator 114. Upon receiving the process workflow diagram 128, the test scenario and test case generator 114 generates a plurality of test scenarios and test cases. In one implementation, the generated test scenarios and test cases can be optimized by the test scenario and test case generator 114 by removing the duplicated test scenarios and test cases. The test scenarios and test cases, thus, generated are uploaded or stored into the test management system 126.
[0038] In one implementation, the test management system 126 invokes the test script
generator 116, which is configured to generate test scripts corresponding to the test cases. The test scripts thus generated are executed by the script executor 118 to test the social media application. The test data generator 120 provides the test data that may be required by the script executor 118 while running a test script on the social media application. The test results of the executed test scripts are stored in the test management system 126 for management and tracking of the testing process.

[0039] An exemplary process workflow diagram 128 for a Design Win application is
depicted in Fig 1(c). In one implementation, the process workflow diagram 128 depicted herein is modeled by the process modeler 112 and exported into a XLS file or any other suitable format. In another implementation, the process workflow diagram 128 depicted herein is a pre-existing diagram imported into the testing system 100. The process workflow diagram 128 is received as an input by the test scenario and test case generator 114. The test scenario and test case generator 114 generates test scenarios based on the process workflow diagram 128. In one implementation, the test scenario and test case generator 114 may be configured to generate the test scenarios in a spreadsheet. Exemplary test scenarios that are generated based on the process workflow diagram 128 are shown in the Fig. 1(d).
[0040] For the test scenarios, the test scenario and test case generator 114 generates a
plurality of test cases. In one implementation, a user may select the test scenarios required for the testing of the social media application. In said implementation, a plurality of test cases is generated for the selected test scenarios. Considering the test scenarios shown in the Fig. 1(d), a plurality of test cases generated for a selected test scenario is shown in the Fig. 1(e). In one example, the test cases may be generated in a spreadsheet.
[0041] The test cases, thus, generated are then automatically uploaded into the test
management system 126 by the test scenario and test case generator 114. For doing so, the test scenario and test case generator 114 may require inputs like the file name of the spreadsheet containing the test cases. It may also require certain information about the test management system 126 like its network address (or URL), login credentials, and the destination folder on the test management system where the spreadsheet will be saved. In one implementation, the above information pertaining to the test management system 126 may be either already available with the test scenario and test case generator 114. In other implementation, the above information pertaining to the test management system 116 can be provided by the user.
[0042] In one implementation, the test management system 126 runs a utility that sends the said spreadsheet as an input to the test script generator 116. The test script generator 116 generates the test scripts and sends the generated test scripts back to the test management system 126, for example, in the form of a XLS file. The test scripts which are made available

to the test management system 126 can then be selected for execution directly from/by the test management system 126. In some implementations, it shall be made possible to select one, many or all of the available test cases for execution. Once the test cases are selected, the test management system 126 then uses the script executor 118 to run the test scripts on the social media application under testing. Any test data required by the test scripts to execute is provided by the test data generator 120. In another implementation, the test data can be manually provided by the user.
[0043] The results of the execution, i.e., the test or execution results, in one implementation, are generated in the form of a test report. The test report may contain. amongst other details, the results of the execution the test script on the social media. application under testing. The script executor 118 then sends the generated test report back to the test management system 126. In one implementation, the result corresponding to the execution of each test script is saved as a file whose naming scheme is indicative of the test scenario, test case, day and time of execution.
[0044] Fig. 2 illustrates a method 200 for automated testing of a social media
application, in accordance with an implementation of the present subject matter. The method may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, etc., that perform particular functions or implement particular abstract data types. The method may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices.
[0045] The order in which the method is described is not intended to be construed as a
limitation, and any number of the described method blocks can be combined in any order to implement the method or an alternate method. Additionally, individual blocks may be deleted from the method without departing from the spirit and scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.

[0046] For the automated testing of a social media application, the method 200 is
initiated at block 202, where a process workflow diagram 128 that is based on the business requirements of the social media application is received as input. The process workflow diagram 128, in one implementation, may be a state transition diagram. In one implementation, the testing system 100 obtains the process workflow diagram 128 as input. In one implementation, the process workflow diagram 128 may be imported into the system from external sources. For example, a user may import a preexisting process workflow diagram 128 or a newly prepared process workflow diagram 128. which is prepared using conventionally known process flow modeling tools, into the testing system. In another implementation, the testing system 100 may be equipped with an in-built process workflow modeler that allows the user to model the process workflow diagram 128s within the system itself.
[0047] At block 204, a plurality of test scenarios is automatically generated based on
the process workflow diagram 128. In one implementation, a test scenario and test case generator 114 associated with or integrated within the testing system 100 generates test scenarios upon receiving business process workflow diagram 128 as input. The test scenario and test case generator is configured to generate the test scenarios based on determining all the possible paths from a start state to an end state in the process workflow diagram 128. These paths may be indicative of a series of actions that are performed when moving from one state to another state in the process workflow diagram 128. Such series of actions correspond to a test scenario. In one implementation, the test scenarios are automatically generated by the test scenario and test case generator 114, for example, TCS Fusion, upon receiving the process workflow diagram 128 as input. The test scenarios, thus, generated covers every possible path in the process workflow diagram 128 from the start state to the end state. In one implementation, the generated test scenarios can be optimized by the test scenario and test case generator 114 based on removal of the duplicated test scenarios.
[0048] At block 206, a plurality of test cases is created for at least one test scenario
amongst the plurality of test scenarios. The at least one test scenario may be a selected test scenario. In one implementation, a user, such as a tester may select one or more test scenarios for which test cases are to be generated. In another implementation, for each test scenario, a

plurality of test cases is generated. Such test cases are generated automatically by the test scenario and test case generator, for example, TCS Fusion.
[0049] For generating the test cases, the test scenario and test case generator 114 may
perform pair-wise testing for each of the states (also referred to as parameters) in the test scenarios. In pair-wise testing, for each pair of parameters in the test scenarios, the test scenario and test case generator 114 may create multiple pair-wise test sets that correspond to the plurality of test cases, for every combination of valid values of the parameters. Further, the test scenario and test case generator 114 may also test all possible discrete combinations of the parameters. Accordingly, the pair-wise testing may catch potential bugs that may be present when specific pairs of items cause an issue. In one implementation, the test scenario and test case generator 114 optimizes the test cases by eliminating duplicated test cases or pair-wise test sets from the plurality of test cases.
[0050] The test cases and/or test scenarios, thus, generated are loaded or stored into a
test management system 126 associated with the testing system 100. The test management system 126 is configured to maintain and store the test cases and/or test scenarios and communicates with the other tools, such as the test script generator and the script executor for testing of the social media application. The test management system 126 acts as a centralized quality management system to facilitates the testing process and maintain tracking and versioning of all the changes and test results. Representative test management systems may include TCS SmartTest Manager for the management and tracking of the testing process. Such a test management system may store testing artifacts, such as test scenarios and test cases.
[0051] At the block 208, a plurality of test scripts is generated for the plurality of test
cases. In one implementation, a test script generator 116, such as TCS RAFT (TCS Reusable Automated Framework for Testing) is associated with or integrated within the test management system 126. The test script generator 116 may be understood as a tool configured to generate executable test scripts. When a social media application is to be tested, the test management system 126 invokes the test script generator 116 to convert the test cases into executable test scripts. The test script generator 116 may be configured to generate the test scripts based on. among other things, the social media application to be tested.

[0052] At the block 210, the test scripts are executed to test the social media
application, such as a sales force application. In one implementation, the test scripts required for testing can be picked up and automatically executed for testing of the social media application. The testing validates the functionality of the social media application under testing to determine whether a change in one part of the social media application has affected other parts of the social media application. If the execution reveals expected results, the social media application under testing can be deployed. While, if the results of the execution are unsatisfactory, the social media application is modified by the development team and retested till expected results are obtained.
[0053] In one implementation, a test script executor 118 executes the scripts generated
at the previous block to test the social media application. Any test data required by the test scripts during the execution may be made available in this step. In one implementation, a test data generator 120 may be associated with the test management system 126 or the script executor 118 to provide the test data upon which the test scripts are executed. In another implementation, test data for testing the application may be manually provided by the user, such as a tester. The results of the testing may be stored in the test management system 126 for tracking and versioning.
[0054] It is to be understood that the specific tools referred in the method 200 are only
for the purpose of examples. The same should not be constructed as a limitation. Any other tools with the same functionality may be used to serve the same purpose, without departing from the scope of the invention.
[0055] Although embodiments for the automated testing of social media applications
have been described in language specific to structural features and/or methods, it is to be understood that the present subject matter is not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as exemplary implementations for automated testing of social media applications.

We claim:
1. A computer implemented method for automated testing of a social media application,
the method comprising:
receiving, by an automated testing system (100), a process workflow diagram (128) created based on business requirements associated with the social media application;
generating, by the automated testing system (100), a plurality of test scenarios based on the process workflow diagram (128);
creating, by the automated testing system (100), a plurality of test cases for at least one test scenario amongst the plurality of test scenarios;
generating, by the automated testing system (100), a plurality of test scripts based on the plurality of test scenarios; and
executing, by the automated testing system (100), the plurality of test scripts on the social media application to generate test results.
2. The method as claimed in claim 1, wherein the generating the plurality of test scenarios comprises determining a plurality of paths in the process workflow diagram 128, wherein each of the plurality of paths corresponds to each of the plurality of test scenarios.
3. The method as claimed in claim 1, wherein the creating the plurality of test cases comprises generating a pair-wise test set for each state in the process workflow diagram 128, wherein each pair-wise test set corresponds to a test case.

4. The method as claimed in claim 1, wherein the creating further comprises receiving the at least one test scenario selected by a user from amongst the plurality of test scenarios.
5. The method as claimed in claim 1, wherein the plurality of test scenarios, the plurality of test cases, and the plurality of test scripts are automatically stored into a test management system (126) connected to the automated testing system (100).
6. The method as claimed in claim 1, wherein the executing comprises obtaining test data for executing the plurality of test scripts on the social media application.
7. An automated testing system (100) comprising:
a processor (102);
a test scenario and test case generator (114), coupled to the processor (102), to,
receive, a process workflow diagram (128) created based on business requirements associated with a social media application to be tested;
generate a plurality of test scenarios based on the process workflow diagram (128); and
create a plurality of test cases for at least one test scenario amongst the plurality of test scenarios;
a test script generator (116), coupled to the processor (102), to generate a plurality of test scripts based on the plurality of test scenarios; and
a script executor (118), coupled to the processor (102), to execute the plurality of test scripts on the social media application to generate test results.
8. The automated testing system (100) as claimed in claim 7 is connected to a test
management system (126), wherein the test management system (126) invokes the test

script generator (116) to convert the plurality of test cases into the plurality of test scripts.
9. The automated testing system (100) as claimed in claim 7 further comprising a test data generator (120), coupled to the processor (102), to provide test data to the script executor (118), for execution of the plurality of test scripts on the social media application.
10. A computer readable medium having embodied thereon a computer program for executing a method for automated testing of a social media application, the method comprising:
receiving, by an automated testing system (100), a process workflow diagram (128) created based on business requirements associated with the social media application;
generating, by the automated testing system (100), a plurality of test scenarios based on the process workflow diagram (128);
creating, by the automated testing system (100), a plurality of test cases for at least one test scenario amongst the plurality of test scenarios;
generating, by the automated testing system (100), a plurality of test scripts based on the plurality of test scenarios; and
executing, by the automated testing system (100), the plurality of test scripts on the social media application to generate test results.