Maestro Performance Testing Approach
Performance testing is one of the key areas of any application, in maestro the performance degradation is mainly observed while loading the widget. Hence we have considered this as a first area to explore and test for performance.
The first challenge for us is, there are millions of combinations of widgets, which one should we consider for testing?
To solve this we are adopting the following approach:
1.Write a query to extract user created widget data. Following widget creating options/combinations will be considered:
d.What to Plot
e.Date range used
2.Run the query and collect the data from all the production clients DB.
3.Identify widely created widgets and its combinations
4.List out all the performance related defects logged in JIRA and Bugzilla. Defects can be logged on production as well as QA sites.
5.Analyze and extract the defects related to widget loading and plotting.
6.Study the database to identify the large tables getting combined while creating the widget.
7.Study the database for complex queries formed during presenting in the UI.
Following data is taken from production Nintendo client.
By observing the data most of the users are creating with
Widget Types: “entity” and “entity sentiment”
Entity Types: “Company” and “Product”
Chart Types: “Line” and “Pie”
What to Plot: “Volume Assets”
-- Will be updating upon further findings