<\/p>\n
While we do follow many of the traditional approaches in testing Fusion 360, we also apply rigor in testing from a Customer perspective.\u00a0 The latter is, in most cases a process of evolution (unless you are talking about software that needs to meet pre-defined policies\/transactions in the industry it serves \u2013 such as legal, banking, or medical<\/em>) as different customers use the tools provided differently.\u00a0 As a result of this, we have seen some stability issues slip through, but we are learning and committed to getting better every day.\u00a0 Our general approach to testing is to develop Modular tests that cascade from unit-level components to workflows used to achieve (a set of) objectives.<\/p>\n <\/p>\n <\/p>\n <\/p>\n DESIGN EXERCISES<\/strong><\/span><\/p>\n <\/p>\n Within the Fusion 360 team, we conduct Design Exercises prior to releasing each update in order to simulate real end-user workflows.\u00a0 These are non-scripted tests that leverage a combination of cognitive team skills\/creativity and a good dose of analytics based on our learning from customer interactions.\u00a0 The general structure of the exercises targets workflow paths one might take to complete a set of design objectives.\u00a0 These could be one or more of the following but not limited to,<\/p>\n <\/p>\n <\/p>\n The steps and approaches followed for each exercise vary and also generally include tools in the product that may be necessary to leverage as part of the workflow (ex., measure, inspect, selections, versions, moving\/copying files in a project, etc<\/em>).\u00a0 The outcome of the exercise produces bugs, CERs as well as exposes performance, reliability, and usability issues.<\/p>\n <\/p>\n Below is an example of one such exercise.\u00a0 Issues uncovered are prioritized based on Severity, Frequency of occurrence, Impact on Customer productivity, Repeatability, and Risk exposure (of the problem as well as from any side-effect the fix could potentially cause<\/em>).<\/p>\n <\/p>\n <\/p>\n <\/p>\n And below is a gallery of some other interesting projects the team has conducted over the past several months.\u00a0 Some of these range from work done by individuals to work done by a team of up to five.<\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n PERFORMANCE<\/strong><\/span><\/p>\n <\/p>\n Also, as part of the Fusion 360 Quality Assurance efforts, we focus on evaluating the performance of the Fusion Client and Cloud Services. \u00a0In addition to the qualitative<\/em> performance evaluations we conduct as part of the Design Exercises, we also run quantitative<\/em> measures using scripted tests. \u00a0These are typically evaluated against a known baseline and where we improve performance, the improved numbers become the new baseline.<\/p>\n <\/p>\n Fusion Client performance is run on physical hardware configured to be repeatable for each run.\u00a0 Degradations noted from the results are debugged and using similar criteria as noted in the previous sections the issue(s) are prioritized for resolution.\u00a0 Fusion Cloud Services performance is run using a Crowdsourced team in order to hit non-Autodesk network connections, provide coverage in connection types & bandwidth, cover geographical variations and different file sizes.\u00a0 These tests are run manually with each tester taking 3 readings at different time(s) of the day that gets averaged to one number per tester.\u00a0 The data is then analyzed to understand performance ranges and debug anything that looks abnormal.<\/p>\n <\/p>\n <\/p>\n ANALYTICS<\/strong><\/span><\/p>\n <\/p>\n We have developed automated dashboards that provide insights (into our Production environments) and allow us to make informed decisions regarding actions to take in improving Customer Experience. These measures are used to drive focus in correcting issues impacting your productivity and at the same time helps us learn and adapt to implementing preventive measures.<\/p>\n <\/p>\n <\/p>\n We have also developed automated dashboards that provide insights into our development environment in order to make informed decisions regarding release readiness and driving focus on key problems.\u00a0 These measures are used to drive and track convergence in quality as well as to prioritize areas of focus for the engineering team.<\/p>\n <\/p>\n This is a process of evolution for us and we are learning every day from you.\u00a0 We are also constantly leveraging opportunities to make the necessary adjustments to our approach and improve it.\u00a0 We would love to hear any comments or suggestions from you.<\/p>\n <\/p>\n <\/p>\n Sanjay Jayabal<\/p>\n","protected":false},"excerpt":{"rendered":" Get an inside view into how the team performs a comprehensive set of tests to the model end-user experience.<\/p>\n","protected":false},"author":88,"featured_media":0,"menu_order":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[12],"tags":[],"coauthors":[],"class_list":["post-333","post","type-post","status-publish","format-standard","hentry","category-news","dhig-theme--light"],"acf":[],"yoast_head":"\n\n
\n
<\/p>\n
<\/p>\n
\n