METHOD AND SYSTEM FOR PERFORMING AN AUTOMATED QUALITY ASSURANCE TESTING

• US 20100180260A1
• Filed: 03/18/2010
• Published: 07/15/2010
• Est. Priority Date: 01/10/2009
• Status: Abandoned Application

• Current Assignee: Testingczars Software Solutions Private Limited
• Original Assignee: Testingczars Software Solutions Private Limited
• Inventors: Govinda, Swethadhry Sharadamba, Basidoni, Girish Narayana Rao, Nagaraja, Ramana Reddy Donthi Reddy, Chikkadevaiah, Madhu Chandan Sunaganahalli
• Application Number:
  US12/726,357
• Publication Number:
  US 20100180260A1
• Time in Patent Office: Days
• US Class Current: 717/125
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

A method includes selecting a plurality of test cases. The method also includes designing the plurality of test cases to perform the automated quality assurance. The method further includes calibrating the plurality of test cases and manage the plurality of test cases in a visual hierarchy. The method also includes reflecting the functional modules in a cohesive group based on the calibration. The method further includes executing the plurality of test cases through at least one of a manual testing mode and an automatic testing mode. The method includes registering information associated with the plurality of test cases. Moreover the method includes generating one or more reports for the plurality of test cases. Furthermore the method includes displaying the one or more reports generated for the plurality of test cases on a visual interface.

Claims

1. An article of manufacture for performing an automated quality assurance, the article of manufacture comprising:

selecting a plurality of test cases;

designing the plurality of test cases to perform the automated quality assurance;

calibrating the plurality of test cases and manage the plurality of test cases in a visual hierarchy;

reflecting the functional modules in a cohesive group based on the calibration;

executing the plurality of test cases through at least one of a manual testing mode and an automatic testing mode;

registering information associated with the plurality of test cases, wherein the registering comprises managing component registry information;

generating one or more reports for the plurality of test cases; and

displaying the one or more reports generated for the plurality of test cases on a visual interface.

2. The article of manufacture of claim 1, wherein the plurality of test cases comprises at least one of:

a set of test data; and

test programs.

3. The article of manufacture of claim 1 comprising:

a set of algorithms for performing at least one of;

capturing a component metadata and a data associated with the plurality of test cases to be tested by a single click;

selecting at least one of the manual testing mode and the automatic testing mode to design the plurality of test cases;

designing the plurality of test cases based on mode of selection; and

associating the data captured with the plurality of test cases.

4. The article of manufacture of claim 3 further comprising at least one of:

capturing user interactions and behavior corresponding to the application under test;

generating one or more test steps required for execution of the plurality of test cases;

capturing one or more input variables automatically for the one or more steps generated;

modifying at least one of the captured user interactions and the one or more input variables; and

defining one or more expected results for the one or more input variables.

5. The article of manufacture of claim 3, wherein the captured component metadata can be used as reference during the modification of the test step.

6. The article of manufacture of claim 4 further comprising the set of algorithms for performing at least one of:

providing an option to select a test step, the test step selected is at least one of mandatory and optional during the capture of the test step;

providing an option to change the sequence of the one or more test steps and to add an additional step during the capture of the test step;

generating a template file to capture an input data for the plurality of test cases, wherein the template file is an external input data file; and

generating test case documentation through selection of at least a test case, a test step and a test.

7. The article of manufacture of claim 6, wherein generating a template file comprises:

overriding a data file associated during the creation of the test case in at least one of the test step and the test case with the external input data file.

8. The article of manufacture of claim 6 further comprising the set of algorithms for performing at least one of:

providing an option to add a test case as a new action to another step in the test case in order to provide the execution flow and to extend, import, and reuse the one or more test cases; and

capturing summary level details of the test case to describe the test case, test conditions, test assumptions, test risks based on a pre-set of language of choice.

9. The article of manufacture of claim 8, wherein the captured summary details comprises at least one of:

a date of creation;

an information pertaining to created user;

a date of modification;

one or more modified details;

a test case purpose; and

a test case status.

10. The article of manufacture of claim 8 further comprising:

creating a project;

managing an execution of the project for application under test;

creating one or more labels for the project time lines;

managing one or more labels for the project time lines, wherein the one or more labels can be used as a tag to apply on the project denoting the phase of the project in the overall Project development life cycle (PDLC);

creating a test suite;

managing an execution of the test suite for application under test;

creating one or more test types; and

managing the one or more test types, wherein the test types can be used as a tag to apply on the test suite denoting the phase of test.

11. The article of manufacture of claim 10, wherein managing the one or more test type comprises:

customizing one or more tags to apply for the test suite and the test case;

applying one or more tags to annotate the test suite and the test case in order to represent the test suite as at least one of the test type during phases of testing; and

promoting the one or more tags to denote the change in the test phase.

12. The article of manufacture of claim 10, wherein the one or more labels created comprises at least one of:

a build;

a release;

a alpha; and

a beta and a general availability.

13. The article of manufacture of claim 10, wherein the one or more test types created comprises at least one of:

a smoke;

an integration;

a sanity system;

a acceptance; and

a regression.

14. The article of manufacture of claim 10 further comprising the set of algorithms for performing at least one of:

defining one or more test scenarios for the project;

creating the plurality of test cases for the one or more test scenarios;

grouping the plurality of test cases relevant to the one or more test scenarios;

associating the plurality of test cases within the test suite;

configuring the one or more test scenarios with one or more component repositories to provide an option to select the runtime environment;

providing an option to execute the one or more test scenarios on the test suite by the single click;

executing the one or more test scenarios through at least one of the manual mode and the automatic mode in a trial run; and

providing an option to stop, pause and restart the execution in the trial run.

15. The article of manufacture of claim 14, wherein the configuring comprises:

selecting a browser of choice to be used for the application under test snapshot of the screen on error;

generating one or more messages to notify status of execution; and

providing an option to define exception handlers.

16. The article of manufacture of claim 14 further comprising the set of algorithms for performing at least one of:

capturing a response from the application under test;

capturing the execution screenshot of the one or more test scenarios with the project phase and the test phase based on a journal system;

validating the response from the application under test;

executing one or more sessions with the one or more test suites;

analyzing one or more results based on the captured response and the execution snapshot; and

generating the one or more reports based on the execution for a category of users.

17. The article of manufacture of claim 16, wherein executing comprises:

executing the one or more sessions in at least one of a background mode, and a foreground mode.

18. The article of manufacture of claim 16, wherein generating comprises:

generating the one or more reports with a dimension of the project phase and the test phase with respect to time based on the journal system.

19. The article of manufacture of claim 16 further comprising the set of algorithms for performing at least one of:

configuring the one or more reports;

merging the reports of the one or more test scenarios to provide a single report for the project; and

providing an option to export the reports in one or more formats.

20. The article of manufacture of claim 19, wherein configuring comprises at least one of:

retaining the one or more reports in complete; and

overriding the one or more reports and retain a latest report generated after execution.

21. The article of manufacture of claim 19 further comprising:

providing the screenshot of the test step that encountered an error during the execution.

22. The article of manufacture of claim 10, wherein creating the project comprises:

creating the project with one or more project details, wherein the one or more project details comprises a description of the project, one or more users of the project, and one or more configuration details of the project.

23. The article of manufacture of claim 22, wherein the one or more configuration details of the project comprises:

a project database;

one or more communication methods;

an user access management; and

an administrator privileges.

24. The article of manufacture of claim 19 further comprising the set of algorithms for performing at least one of:

providing an option to modify the one or attributes related to the component;

providing an option to select a database for the project across a network;

creating the one or more users and assign permissions, wherein the one or more users and assign comprises a create, a view and a delete; and

terminating the project for at least one of use and re-activate of the project.

25. The article of manufacture of claim 18, wherein the one or more reports generated comprises at least one of:

a high level report;

a low level report;

a summary report;

a module report;

a test case report; and

a test step report.

26. The article of manufacture of claim 24 further comprising the set of algorithms for performing at least one of:

capturing one or more events to generate an event log for the purpose of traceability and audit of purpose; and

providing an option for a user to login and get authenticated with a central admin system in order to receive the users profile, meta-data, access to projects and permissions.

27. The article of manufacture of claim 1, wherein the automated quality assurance software testing is performed through a script less approach.

28. A computer-implemented method for performing an automated quality assurance, the computer-implemented method comprising:

selecting a plurality of test cases;

designing the plurality of test cases to perform the automated quality assurance;

calibrating the plurality of test cases and manage the plurality of test cases in a visual hierarchy;

reflecting the functional modules in a cohesive group based on the calibration;

executing the plurality of test cases through at least one of a manual testing mode and an automatic testing mode;

registering information associated with the plurality of test cases, wherein the registering comprises managing component registry information.

generating one or more reports for the plurality of test cases; and

displaying the one or more reports generated for the plurality of test cases on a visual interface.

29. The method of claim 28, wherein the plurality of test cases comprises at least one of:

a set of test data; and

test programs.

30. The method of claim 28 comprising:

a set of algorithms for performing at least one of;

capturing a component metadata and a data associated with the plurality of test cases to be tested by a single click;

selecting at least one of the manual testing mode and the automatic testing mode to design the plurality of test cases;

designing the plurality of test cases based on mode of selection; and

associating the data captured with the plurality of test cases.

31. The method of claim 30 further comprising at least one of:

capturing user interactions and behavior corresponding to the application under test;

generating one or more test steps required for execution of the plurality of test cases;

capturing one or more input variables automatically for the one or more steps generated;

modifying at least one of the captured user interactions and the one or more input variables; and

defining one or more expected results for the one or more input variables.

32. The method of claim 30, wherein the captured component metadata can be used as reference during the modification of the test step.

33. The method of claim 31 further comprising the set of algorithms for performing at least one of:

providing an option to select a test step, the test step selected is at least one of mandatory and optional during the capture of the test step;

providing an option to change the sequence of the one or more test steps and to add an additional step during the capture of the test step;

generating a template file to capture an input data for the plurality of test cases, wherein the template file is an external input data file; and

generating test case documentation through selection of at least a test case, a test step and a test.

34. The method of claim 33, wherein generating a template file comprises:

overriding a data file associated during the creation of the test case in at least one of the test step and the test case with the external input data file.

35. The method of claim 33 further comprising the set of algorithms for performing at least one of:

providing an option to add a test case as a new action to another step in the test case in order to provide the execution flow and to extend, import, and reuse the one or more test cases; and

capturing summary level details of the test case to describe the test case, test conditions, test assumptions, test risks based on a pre-set of language of choice.

36. The method of claim 35, wherein the captured summary details comprises at least one of:

a date of creation;

an information pertaining to created user;

a date of modification;

one or more modified details;

a test case purpose; and

a test case status.

37. The method of claim 35 further comprising:

creating a project;

managing an execution of the project for application under test;

creating one or more labels for the project time lines;

managing one or more labels for the project time lines, wherein the one or more labels can be used as a tag to apply on the project denoting the phase of the project in the overall Project development life cycle (PDLC);

creating a test suite;

managing an execution of the test suite for application under test;

creating one or more test types; and

managing the one or more test types, wherein the test types can be used as a tag to apply on the test suite denoting the phase of test.

38. The method of claim 37, wherein managing the one or more test type comprises:

customizing one or more tags to apply for the test suite and the test case;

applying one or more tags to annotate the test suite and the test case in order to represent the test suite as at least one of the test type during phases of testing; and

promoting the one or more tags to denote the change in the test phase.

39. The method of claim 37, wherein the one or more labels created comprises at least one of:

a build;

a release;

a alpha; and

a beta and a general availability.

40. The method of claim 37, wherein the one or more test types created comprises at least one of:

a smoke;

a integration;

a sanity system;

a acceptance; and

a regression.

41. The method of claim 37 further comprising the set of algorithms for performing at least one of:

defining one or more test scenarios for the project;

creating the plurality of test cases for the one or more test scenarios;

grouping the plurality of test cases relevant to the one or more test scenarios;

associating the plurality of test cases within the test suite;

configuring the one or more test scenarios with one or more component repositories to provide an option to select the runtime environment;

providing an option to execute the one or more test scenarios on the test suite by the single click;

executing the one or more test scenarios through at least one of the manual mode and the automatic mode in a trial run; and

providing an option to stop, pause and restart the execution in the trial run.

42. The method of claim 41, wherein the configuring comprises:

selecting a browser of choice to be used for the application under test snapshot of the screen on error;

generating one or more messages to notify status of execution; and

providing an option to define exception handlers.

43. The method of claim 41 further comprising the set of algorithms for performing at least one of:

capturing a response from the application under test;

capturing the execution screenshot of the one or more test scenarios with the project phase and the test phase based on a journal system;

validating the response from the application under test;

executing one or more sessions with the one or more test suites;

analyzing one or more results based on the captured response and the execution snapshot; and

generating the one or more reports based on the execution for a category of users.

44. The method of claim 43, wherein executing comprises:

executing the one or more sessions in at least one of a background mode, and a foreground mode.

45. The method of claim 43, wherein generating comprises:

generating the one or more reports with a dimension of the project phase and the test phase with respect to time based on the journal system.

46. The method of claim 43 further comprising the set of algorithms for performing at least one of:

configuring the one or more reports;

merging the reports of the one or more test scenarios to provide a single report for the project; and

providing an option to export the reports in one or more formats.

47. The method of claim 46, wherein configuring comprises at least one of:

retaining the one or more reports in complete; and

overriding the one or more reports and retain a latest report generated after execution.

48. The method of claim 46 further comprising:

providing the screenshot of the test step that encountered an error during the execution.

49. The method of claim 37, wherein creating the project comprises:

creating the project with one or more project details, wherein the one or more project details comprises a description of the project, one or more users of the project, and one or more configuration details of the project.

50. The method of claim 49, wherein the one or more configuration details of the project comprises:

a project database;

one or more communication methods;

an user access management; and

an administrator privileges.

51. The method of claim 46 further comprising the set of algorithms for performing at least one of:

providing an option to modify the one or attributes related to the component;

providing an option to select a database for the project across a network;

creating the one or more users and assign permissions, wherein the one or more users and assign comprises a create, a view and a delete; and

terminating the project for at least one of use and re-activate of the project.

52. The method of claim 45, wherein the one or more reports generated comprises at least one of:

a high level report;

a low level report;

a summary report;

a module report;

a test case report; and

a test step report.

53. The method of claim 51 further comprising the set of algorithms for performing at least one of:

capturing one or more events to generate an event log for the purpose of traceability and audit of purpose;

providing an option for a user to login and get authenticated with a central admin system in order to receive the users profile, meta-data, access to projects and permissions; and

54. The method of claim 28, wherein the automated quality assurance software testing is performed through a script less approach.

55. A system for performing an automated quality assurance comprising:

a server, the server comprises;

a administrator module; and

a client module for;

selecting a plurality of test cases;

capturing a component metadata and a data associated with the plurality of test cases to be tested by a single click; and

selecting at least one of the manual testing mode and the automatic testing mode to design the plurality of test cases.

56. The system of claim 55, wherein the client module comprises:

a processor, the processor for;

designing the plurality of test cases to perform the automated quality assurance;

calibrating the plurality of test cases and manage the plurality of test cases in a visual hierarchy;

reflecting the functional modules in a cohesive group based on the calibration;

executing the plurality of test cases through at least one of a manual testing mode and an automatic testing mode;

registering information associated with the plurality of test cases, wherein the registering comprises managing component registry information; and

generating one or more reports for the plurality of test cases.

a visual interface for;

displaying the one or more reports generated for the plurality of test cases in a grid format with project phase being denoted in the timeline of the project in one axis and the test type being denoted in the phase of testing as another axis on a visual interface in the client module.

57. The system of claim 56, wherein visual interface for:

displaying a list of one or more captured components, the list of the one or more captured components is used as reference during modification of a test step and creation of the test step;

displaying disparate set of one or more component repositories that can be switched during the modification of the test case;

providing an option to upload an external file, the external file comprising one or more input data to be used during the execution of the test step;

providing an option to allow the user to browse for one or more test cases;

displaying a pre-defined list of actions to perform one or more tasks during the execution of the test step;

displaying the one or more execution details;

displaying the status of the project with one or more details, wherein the one or more details comprises at least one of a number of active projects, a number of logged in users and a list of logged in users for the project; and

displaying the one or more projects automatically to a user, the user as access to sub-systems and the visual interface.

58. The system of claim 56, wherein the processor comprises:

a designer for designing the plurality of test cases to perform quality assurance software;

an executor executing the plurality of test cases through at least one of a manual testing mode and an automatic testing mode;

a registry for registering information associated with the plurality of test cases; and

a reporter for generating one or more reports for the plurality of test cases based on the registration of information.

59. The system of claim 57, wherein the displaying the one or more execution details comprises:

a progress of execution;

a number of test cases passed;

a number of test cases failed; and

a number of test cases skipped along with the execution start time.

60. The system of claim 56, wherein the visual interface for:

providing an option to manage a component repository.

61. The system of claim 60, wherein the component repository comprises:

a list of one or more components captured across the user interface of the application under test.