DESC:Field of the Invention
The present invention relates to a system and a method for the objective assessment of an application available on a public mobile application store. More specifically, the present invention performs tests on various applications that are designed to run on a mobile operating system and provides an objective score.

Background of the Invention
Mobile devices have become an inseparable part of the daily routine of people across the globe. Mobiles provide with various features for easy connectivity and communication among people. The functionality of the mobiles increases by installation of third party applications. The success of such applications on mobiles has led to the development of applications that can run on different mobile operating systems and hence arises a need for the assessment of the applications. The evaluation of an application requires a proper system for assessment and a suitable procedure to be followed to provide a score to the application based on functionality, usability and performance of the application.

Such a method has been disclosed in CN 105117544 A. The said method comprises the steps of collecting all applications in an android market, and obtaining a permission list of each application; uploading data of the obtained permission list to the cloud; performing risk grade judgment according to the application privacy permission in the permission list and the set privacy permission risk mark in accordance with the obtained permission list of each application; and requesting data to the cloud according to the request of a mobile phone client, and sending the corresponding application risk grade judgment result obtained from the cloud and the privacy permission called by the application to a customer.
Such a system and method have been disclosed in US 9215548 B2. The method comprises the steps of receiving, by a computing system, a copy of a mobile platform application designed for execution on a mobile platform, the copy including a stated purpose for the mobile platform application, the mobile platform having one or more files including personal information stored thereon; determining, by the computing system, (i) an intended purpose of the mobile platform application, (ii) one or more files stored on or included in the mobile platform or functionalities afforded by the mobile platform that are accessed by the mobile platform application during its operation on the mobile platform, (iii) whether said accesses include accesses to the personal information and, if so, whether said accesses are consistent with the intended purpose and the stated purpose of the mobile platform application, and (iv) an overall score for the mobile platform application based upon said determinations; determining a user configurable weighted rating for each of the discrepancies according to its impact on a user's privacy and based on the user's preferences; calculating a weighted average based upon the weighted rating assigned to each of the discrepancies; and calibrating the weighted average to determine the overall score; and presenting the overall score to a potential user of the mobile platform application.

Such a system has been disclosed in US 9119015 B2. The said system comprises of a telecommunications device comprising a processor component and a monitoring component; and an analyzing component configured to analyze the performance data and to identify characteristics of the plurality of applications. The said method comprises the steps of running a plurality of applications via a processor component; monitoring the plurality of applications and generating performance data via a monitoring component; analyzing the performance data and identifying characteristics of the plurality of applications via an analyzing component; causing communications destined for a data network to use an alternative data route between the device and the data network via the analyzing component; and monitoring, via the monitoring component, the plurality of applications when communications are transmitted via the alternative data route.

The systems and methods for evaluating and rating an application designed to run on mobile devices as described in the prior art does not provide an objective rating of said applications as the ratings may be either manipulated positively by certain agencies that are specialized in such activities or negatively impacted by the users who may give an emotion based rating and hence may lead to a rating which does not reflect the actual quality of the application.

Objective of the Invention

The objective of the invention is to devise a system and a method for the evaluation of an application that is available on a public mobile application store and provides a score that is objective and cannot be manipulated by any means. The rating that is made available to the users shall provide accurate information regarding the quality and the performance of the application
The present invention achieves the objective by employing a system and method for the assessment of an application designed to run on a mobile operating system and provide an objective score based on the functionality, usability and performance of the application. The application is tested through checklist tests that are segregated into different lists based on the aspect of the application that is required to be evaluated.

Summary of the Invention
The present invention relates to a system for assessment and rating of an application that is available on a public mobile application store. The said system comprises of a software product for manually testing the data related to the application and computing the score; and a checklist of tests that are to be executed on the application.

According to the invention, the score for the application is generated by an algorithm that takes into consideration various quality aspects of the mobile application which includes functionality, usability and performance. The aspect of number of issues discovered in the application is also evaluated while the tests are being performed. In computation of the score, different weightage is provided to distinct quality aspects as the impact of all the aspects on the application is non-identical.

The multiple factors, determining the quality of the mobile application, that are taken into consideration by the algorithm includes, not limiting to, type of issue, severity of issue, weightage for each type of issue and weightage of each severity level per type of issue.

According to an embodiment of the invention, the types of issues that are evaluated for the computation of the score include, not limiting to, functionality, usability and performance.

According to an embodiment of the invention, the severity of the issues discovered in the mobile application is categorized into the categories including, not limiting to, Critical, High, Medium and Low.

The tests are performed on the application manually by trained software testers examining the various aspects of quality of the application. The information received from the manual testing and the issues discovered in the application are recorded in the software product. The software product is created with the purpose of recording said information and enables the objective scoring of the application reflecting the overall mobile application experience for the end users.

The test scenarios, developed by way of performing tests on various mobile applications, are coded into the software product and embedded in the form of checklist of tests that enables computation of the score to the quality of the application. The checklists are segregated into distinct lists based on the aspect of the quality of the application that is required to be assessed. The manual tester selects PASS/FAIL for each test scenario that is to be executed upon the mobile application and have the option to create a new test scenario manually for each application that is to be tested.

The present invention also relates to a method for assessment and rating of an application that is available on a public mobile application store. The said method comprising the steps of uploading a debug enabled application file to the software product; viewing the checklists used for testing various test scenarios on the mobile application; marking the result of each test with an appropriate response; adding new test scenarios specific to the application being tested; marking the result of tests performed with appropriate response; submission of the test result; computation of the score with the help of an algorithm and display of the report; reviewing the new test cases; and publishing the test report.

The display of the test report is demarcated into sections including overall rating for the mobile application; basic information about the mobile application from the store; number of test cases that failed from the tests of the scenario; checklist test cases that failed for a scenario of mobile application quality; number of issues discovered in a scenario in each severity level i.e., critical, high, medium and low; list of quality issues discovered in the mobile application; and recommendations and suggestions for improvement in the mobile quality application.

The maximum value of the score that can be assigned to the application is 5 which indicate that the application was not discovered with any quality issues, whereas the minimum value of the score is 0 which indicates that the application was discovered with too many quality issues of high severity levels. The intermediate value of the score ranges between 0-5 and does not range in negative, and in case of decimal score the value is round off to single decimal digit.

Brief Description of the invention

The present invention relates to a system and method for objective assessment and rating of an application designed to run on a mobile operating system and available on a public mobile application store. The system for evaluation comprises of a software product and a checklist of tests. The system computes the score for the quality of the application by the method that comprises of the following steps:

1. Uploading of the debug-enabled mobile application file to the software product that is hosted on a cloud and accessed through a web browser.

2. Testing of the various test scenarios on the mobile application by the software tester that uses the software product for viewing the checklists that are used as a reference.

3. Marking of the result, by the software tester, of the test of each test scenario in the checklist with an appropriate response that can be either PASS or FAIL.

4. Logging a bug by the tester by way of selecting the most appropriate description and attaching the files, if any, in case a pop up window appears due to the failure of a test scenario during test execution.

5. Adding new test scenarios by the software tester using the software product page for including the test scenarios that are specifically applicable only to that particular mobile application’s usage. The addition of new test scenarios is performed after all the previous checklist checks are completed.

6. Marking of the result, by the software tester, for the tests of each new test scenario with an appropriate response that can be either PASS or FAIL.

7. Submission of the test report, by the software tester, after completion of the tests on the mobile application using the software product page.

8. Computation of the objective score by the software product based on the algorithm. The computed score is then displayed on the test report.

9. Receiving of the test report in the software product and reviewing of the new test cases submitted specifically for a particular mobile application and updating the test scenarios or accepting the test scenarios and approving the test report.

10. Publication of the test report after all the required changes is completed and then is made available to the mobile application owner in various formats as per the requirement.

Brief and Detailed Description of Drawings
Figure 1 illustrates the functional checklist page of the application.
Figure 2 illustrates the severity of issue discovered in the application.
Figure 3 depicts file upload page of the application.
Figure 4 illustrates the perform test page of the application.
Figures 5 and 6 depicts rating page of the application.
Figure 7 illustrates the detailed test report.
Figure 8 illustrates the application rating page.
Figure 9 depicts the severity versus bugs page of the application.
Figure 10 illustrates the application specific checks.
Figure 11 illustrates the graphical representation of the test score.
Figure 12 illustrates the bug identification page of the application.
Figure 13 illustrates the recommendation page.

The Figures 1-13 illustrates the process of testing of an application and producing the rating of said application. The Application Quality Check is a process through which any applications’ quality score. Quality score essentially is a relative score which depicts the end user experience of the application. The process involves the application to go through 300+ checks to test various quality parameters like Release Readiness, Application Usage, Clarity, Intuitiveness, Functionality, install-ability, performance etc.

The entire process is divided into different sections to identify quality parameters for the application. The checks are done with the help of different checklists created specifically for various parameters. In the first step, the owner of the application is asked to upload the application on Application Quality Check platform. On said platform, owner can choose the type of test to be performed on the application. These tests are MooRelease, Mooessential and MooPerform. The difference in these types of tests are to have tests moving from basic checks in MooRelease to most advance checks in MooPerform.

The outcomes of the process for the application owner are defect lists and recommendations. Every test that the process does has a relative weight. These weights are considered for the quality score of that particular parameter and overall quality score.

Example
The tests are performed on various mobile applications resulting into the creation of checklists of checks categorized into different types based on the aspect of the quality of the mobile application that is required to be evaluated.
Example 1: Functionality Checklist
# Functionality Checklist
1 Does the title and logo of the application is self-explanatory
2 Check for size of the application. If the overall size of the application greater than 100 MB please make a note of it
3 Does the application check for enough memory space before installation begins? If memory is not enough, does it throw error before installation?
4 Confirm the Application's Platform and Screen Compatibility Ranges
5 Does your application have enough screenshots and videos in the playstore
6 Check for Application installation on SD card, if device supports SD card
7 Check if there is any information mentioned about the application or the developer. Check if there are any claims listed in the play store.
8 While installing the application, if user cancels the download, installation should stop successfully.
9 Does the Application behave properly when application permission is revoked after installation?
10 Check for the consistency of the Application name in the playstore and in the Application after installing.
11 After installation of the application, check if the application can be launched successfully from the Play Store also.
12 Check for the consistency and presence of logo and icon on all the screens of the application.
13 Does your application support worldwide audience? If so, check for language localization. Eg. All UI elements, text, notifications, error messages etc are changed to preferred language
14 Check if the support provided is also in the preferred language.
15 Verify that respective country code is displayed if any.
16 Determine whether the primary functionality of the application allows in achieving the task it is intended to do.
17 Determine whether functionalities make use of standard gestures that are designed to achieve a specific task.
18 Determine whether each functionality is unique in its style and characteristic to ensure effortless usage.
19 Does your application restore back from interruptions? Calls, SMS, Emails, Camera, Notifications etc.
20 Does your application support orientation? If Yes:
a. Does the content align as per the orientation changes?
b. Are you able to read the content?
21 Does your application support standard gestures like tap, double tap, pinch open/close.
22 Is the navigation between different screens smooth?
23 Does the notification drawer contain more than one icon in case of multiple notifications for a single application?
24 Set Application notification to ON/OFF and see if it still continues to send/stop updates.
25 Notifications do not contain advertising or unrelated content.
26 Does the Application correctly handles rapid transitions between display orientations without rendering problems.
27 When the application is resumed from the Recents application switcher, the application returns the user to the exact state in which it was last used.
28 When the application is resumed after the device wakes from sleep (locked) state, the application returns the user to the exact state in which it was last used.
29 When the application is relaunched from Home or All Applications, the application restores the application state as closely as possible to the previous state.
30 On Back keypresses, the application gives the user the option of saving any application or user state that would otherwise be lost on back-navigation
31 Check if there is any share option, and shared successfully. Also, make sure all social media sharing applications are listed.
32 Try to install application on different Operating System versions other than the one that application supports.
33 Check for helpfulness of the error message in case of installation issues
34 Check if any warning message is displayed before uninstalling the application.
35 Check if user is able to uninstall the application successfully.
36 Verify that uninstallation is consistent for all the Android devices.
37 Is there any option in the application which helps the user to rate the application?
38 Navigate to all parts of the application — all screens, dialogs, settings, and all user flows.
39 From each application screen, press the device's Home key, then re-launch the application from the All Applications screen.
40 From each application screen, switch to another running application and then return to the application under test using the Recents application switcher.
41 From each application screen (and dialogs), press the Back button.
42 From each application screen, rotate the device between landscape and portrait orientation at least three times.
43 Switch to another application to send the test application into the background. Go to Settings and check whether the test application has any services running while in the background. In Android 4.0 and higher, go to the Applications screen and find the application in the "Running" tab.
44 Launch Application from Notifications. Does tapping on a notification launch right UI?
45 Does the application's landing screen creates a positive impression and does not throw too many options to user?
46 Launch the application, Lock the phone & Unlock it. Observe applicationbehavior. Does the application launch same UI from where you left or show Home Screen? Do you see any distortion in the UI?
47 If the application has any sections for playing audio/videos.Start the video, pause the video, lock the phone & unlock, resume.
48 Network Interruptions are handled smoothly.

Example 2: Usability Checklist
# Usability(UX+UI) Checklist
1 Design Clean and Clutter free - Clarity
2 Icons are clear to understand - No ambiguity
3 Change the Font Size and Type on the Device - See how it affects the application's content and UI
4 Determine whether the User Interface is clean and neat with UI elements placed appropriately
5 Determine whether each UI element is unique in its style and characteristic
6 Enough Spacing between button label and the button
7 Label/Image is relevant to the action performed on tapping the button
8 Clarity of purpose in Label/Image
9 Label is short and understandable
10 Images are not overlapping with other elements or content in the site
11 To place checkbox to the right of the label, which is more user friendly
12 If there are any advertisements, the option to close the advertisements should be on the left side of the advertisement displayed.
13 Identify whether each functionality in the application is easy to understand and simple to use.
14 User can easily open and close the calendar
15 If the login is through Email or Phone number that respective placeholder text should display only the valid text not both.
16 Determine whether each UI elements has a consistent design across the application.
17 Consistency of the image height and width with other elements and images
18 Use of standard icons and images for easy identification. For example Icon used to represent calendar is easily identifiable.
19 Enough spacing between checkbox and the label.
20 Is checkbox label and tick mark font user friendly?
21 No punctuation should be used at the end of checkbox label.
22 Single checkbox for a yes or no choice.
23 Hyperlink label need to be consistent with linked page title/headings.
24 Consistency in Naming for hyperlinks.
25 Field length or width is proportional to allowed field length/width (based on the context)
26 Character Masking for confidential text fields (E.g. password field)
27 Character Masking for confidential text fields (E.g. password field)
28 Validation of dates are meaningful (Eg.: Not allowing a user to add the current date as date of birth)
29 Does user has control over the Zoom In option?
30 Applications information and capabilities can be discovered by exploration of the user interface – Discoverability
31 Reason behind disabled dates are easily understandable to user (Eg: Dates before the current date are disabled on an application for booking movie tickets)
32 Is there an indication near the field about the date format followed?
33 Sufficient clues that a clickable item is clickable.
34 Cancel' or 'Stop' option if the action is going to take a long time.
35 Error messages are clear and informative - Error Handling
36 Determine whether the application gives appropriate feedback whenever some Input is provided
37 Determine whether the application uses contextual keypad to ensure ease of providing inputs.
38 Application has easy-to-understand states and possibilities of interacting with the application - Interactivity
39 Identify whether the application is engaging the user with feedback at appropriate times indicating the progress of the activity initiated
40 All the labels are in title case
41 Availability of scroller if the data is large compared to the available width and length (TextArea)
42 Cursor position needs to be highlighted to indicate the control
43 UI does not break upon changing orientation
44 Is field validation implemented? (Give user info about any invalid character)
45 Autosuggest list disappears on selecting an item from the list
46 Visual change when the screen is navigated to another screen is smooth
47 Easy to understand and explain what the application can do - Intuitiveness
48 Determine whether the UI is designed with pleasant colors and combinations
49 Use of less text and more icons and graphs will make application usage easy and user –friendly
50 Determine whether the UI elements are designed with enough realism and physicality
51 Does button have an image?
52 Does button have a label?
53 Does button have an image and a label?
54 High contrast color used for button to grab user attention
55 Easy navigation through the months
56 Label/Image is relevant to the action performed on selecting checkbox
57 Visual change on the checkbox to indicate the user when the option is selected
58 Speed in which the autosuggestion is displayed
59 Easy navigation between the screens
60 Easy to zoom in/out using standard gestures like pinch zoom/out, double tap
61 Determine whether the appearance of a control that performs a standard action is constant throughout the application.
62 UI of the application is not too heavy that in turn affects the performance of the application
63 Any area on the button is tap able
64 Navigation to Home Page from any part of the product
65 Responsiveness on multiple platforms and devices
66 Image load time is less or not too high
67 Is there a close button on the expanded Calendar?
68 User can easily select a date
69 Any area on the checkbox is tappable
70 Tapping on navigation menus
71 Tap able images should be tap able anywhere on the image
72 Is the progress indicator displayed as soon as an action is performed
73 User is not to be blocked from using the system until the task is completed or it can process in parallel with other actions on the system
74 Is there an option to restore to the original state?
75 Fast and Easy to learn about how to use the application - Learnability
76 Avoid having typographical errors which makes user spend more time learning what it means.
77 Help section, Support, Terms and Conditions - Documentation
78 Determine whether the UI elements are picked from the standard set of buttons and icons to avoid ambiguity
79 Determine whether the UI elements are designed using appropriate font type and size for better readability
80 Label is readable
81 Noticeable Field Constraints (length or character types)
82 Field Length Indicator (Track how many more characters can be entered)
83 Input text is readable
84 Field Alignment (E.g. Numbers are right aligned)
85 User should be able to correct mistakes easily (error handling).Eg:- User made a mistake while entering password in the 'confirm password' field, he/she should be able to figure it out easily with error handling and correct the mistake before moving on to the next field
86 Relevancy of the label associated with the textbox, if any
87 Short and clear label, if any
88 Default date displayed is meaningful to the context
89 Selected date reflecting on the consecutive field is clear to the user
90 The format in which the date is displayed is easily understandable to the user
91 Default date is highlighted in the calendar
92 Use chronological order for alphabetical lists
93 Does checkbox have a label?
94 Does checkbox have an image?
95 Does checkbox have both label and image associated?
96 Short and crisp check box labels
97 Non-clickable items are not to have properties of clickable items (E.g. hand icon, highlighted etc)
98 Autosuggestion lists are easily readable
99 Relevancy against the input field (Eg:- If an autosuggest is displayed for a 'city' field, only cities name should be displayed)
100 Is there a limit on the number of items displayed (For ex:- Most relevant 10 items are displayed)
101 Is there a use of Progress Indicator (If an action is not taking more than 2 seconds to accomplish, the use of progress indicator will be a waste
102 Space progress updates evenly (Eg:Avoid situations where progress increases to over 80% and then stops for a long period of time. You want to speed up progress towards the end, not slow it down. Avoid drastic jumps, such as from 0% to 90%.)
103 User should easily understand if the action has stopped or if there is a obstacle

Example 3: Application Launch Readiness Checklist
# Application Launch Readiness Checklist
1 Store has enough description of the product along with images, videos and product claims
2 Check for storage space before installation and give appropriate error message
3 Asks for permissions from the user before installation
4 Successfully install the build on all supported devices
5 Application opens successfully when launched from home screen
6 Allows user to carry out actions (Checkout, Browsing etc)
7 Application does not crash while it is in use
8 Navigation between different screens is smooth and easy
9 Able to launch application from background
10 Application resumes back smoothly from idle state
11 Application handles network fluctuation gracefully
12 Able to uninstall application when user wishes to do so
13 Able to close/quit application from any part of the application
14 UI of the application does not break or get haywire when the device is positioned differently.
15 Gestures used in the application are standard or recommended by Android guidelines
16 Saves changes made by end user in application Settings (Notifications, Profile)
17 Recovers smoothly from interruptions like call, sms, notifications etc
18 UI of the application is intuitive or self explanatory
19 Application does not misalign due to change in orientation
20 Help section or FAQ which answers common concerns and questions of end user
21 Email,SMS,Call or Chat support in case of immediate help
22 All UI elements in all the screens are functionally and visually tappable
23 Contextual keypad opens up wherever needed
24 When application is used constantly for 30+ minutes no crashes as seen. (Out of Memory exception is handled well)
25 Application acknowledges actions performed by user such as payment transactions, Save card details, Delete Card
26 Error, alert, warning, toast messages are crisp and clear
27 Has enough description of the application features along with screenshots and videos
28 Bug fixes details and new changes or feature enhancements
29 Name on the application icon and it's store is a perfect match
30 Special offers, discounts or any other information that benefits user is highlighted in the description
31 In-application purchase details are mentioned in the store
32 Device/Operating System compatibility constraints are mentioned

Example 4: Performance Checklist
The checks provided in the following checklist tests the performance of the mobile application.
# Performance Checklist
1 CPU usage when application is in the background is a minimum value
2 CPU usage is efficiently handled when application in use
3 CPU Usage is optimized during idle state
4 CPU usage is efficiently handled when application in use
5 CPU usage is efficiently handled when application in use
6 Recovers to the previous state where it was left before pushing application in background
7 Application does not hang or crash when launched from background
8 Application does not hang or crash when launched from background
9 Application does not take long (beyond 2-3 s) time to launch splash screen or display landing screen after an action
10 After having kept application in idle state in foreground with screen unattended for long time(around 15-20 min) restores original state when an action is performed
11 Does not cause memory heap while not in use or in background
12 Application does not cause large memory heap leading to crash when used extensively or continuously due to infinite scrolling
13 Application does not cause image/content rendering issues when orientation is changed
14 No heap memory issue is caused during idle state and application does not crash after performing action
15 No skipping of frames or choreographer issues seen when application is in foreground
16 Application does not consume battery when it is pushed in background
17 Battery consumption in the foreground is efficiently handled
18 Battery usage is minimized when the application is not in use
19 Battery consumption in the foreground is efficiently handled
20 Application does not consume battery when it is pushed in background
21 No GPU overdrawn screens/areas in the application
22 Under No Network condition when the application is launched, it throws network error message
23 When the network fluctuates (ON-OFF, vice-versa) in quick succession while the application is in use, application resume back smoothly after the connection is restored.
24 Application is capable of smoothly handling network switching scenario such as Wifi-3G/2G or vice versa
25 Application performance does not degrade when used under fairly good hotspot/tethering conditions
26 Application does not send/receive any data or use network data while in background
27 Data sent/received over network is not heavy
28 Data sent/received over network is not heavy
29 No data is sent or received during idle state
30 Text file compression
31 Duplicate Content
32 Cache Control
33 Content Expiration
34 Combine JSS and CSS Requests
35 Resize Large Images for Mobile
36 Minify CSS, JS, JSON and HTML
37 Use CSS Sprites for Images
38 Connections Opening
39 Multiple Simultaneous Connections
40 Inefficient Connections - Periodic Transfer
41 Inefficient Connections - Screen Rotation
42 Inefficient Connections - Connection Closing Problem
43 400, 500, HTTP Response Codes
44 301, 302 HTTP Response Codes
45 3rd Party Scripts
46 Asynchronous load of Javascript in HTML
47 HTTP 1.0 Usage
48 File Order
49 Empty Resource & File Attributes
50 FLASH
51 "'display:none" in CSS
52 Other: Accessing Peripheral Connections

,CLAIMS:We Claim:
1. A method of assessment and rating of an application designed to run on a computing device, said method comprising the steps of:
i. uploading a debug enabled application file;
ii. viewing the checklists used for testing various test scenarios on said application;
iii. marking the result of each test with an appropriate response;
iv. adding new test scenarios specific to the application being tested;
v. marking the result of said new tests performed with appropriate response;
vi. submission of the test result;
vii. computation of score and display of report;
viii. reviewing the new test cases; and
ix. publishing the test report;
characterized in that said method evaluates the functionality; usability and performance aspects of said application.

2. The method as claimed in Claim 1, wherein said method involves the evaluation of number of issues, type of issue and severity of issue discovered in the application.

3. The method as claimed in Claim 1, wherein the test scenarios are converted to checklist of tests based on functionality, usability and performance of said application.

4. The method as claimed in Claim 1, wherein the maximum value of the score is 5 and the minimum value of the score is 0.

5. The method as claimed in Claim 1, wherein the test report published comprises of:
i. overall rating for said application;
ii. basic information about the application;
iii. number of test cases that failed out of all tests run for a scenario;
iv. checklist test cases that failed for a scenario of said application quality;
v. number of issues discovered in a scenario in each severity level;
vi. list of quality issues discovered in the application;
vii. recommendations and suggestions to improve the quality of the application.

6. A system of assessment and rating of an application designed to run on a computing device, said system comprising of:
a memory for saving database;
a server that runs on an operating system; and
a processor for processing database;
where said system further comprises of:
i. a tool for manually testing the data;
ii. a checklist of tests; and
iii. a tool for computing the score;
wherein said system is configured to evaluate distinct quality aspects of said application.
7. The system as claimed in Claim 6, wherein said system assigns different weightage to different aspects of quality of said application.

8. The system as claimed in Claim 6, wherein said system records and saves the data from manual testing of the application and the issues discovered in said application.

9. The system as claimed in Claim 6, wherein the checklists of test includes Functional Checklists, User Interface Checklists, User Experience Checklists and Performance Checklists.