So far there is no error catching in the workflow of test reporting, users will run into an unclear failure such as "Range error: Invalid string length". We want to make sense of the frequency of the error and how many users have run into the error. We need to add error catching to report the failures so we could better decide our next steps for the issue.
What issues does this PR fix or reference?
@W-15226968@
Functionality Before
Users receive unclear error messages like "Range error: Invalid string length" when stringify fails
Functionality After
Users receive specific and clear error messages with advice so it is easy to understand and we are able to catch the errors in each bottleneck to make sense of the frequency of the bottlenecks.
What does this PR do?
So far there is no error catching in the workflow of test reporting, users will run into an unclear failure such as "Range error: Invalid string length". We want to make sense of the frequency of the error and how many users have run into the error. We need to add error catching to report the failures so we could better decide our next steps for the issue.
What issues does this PR fix or reference?
@W-15226968@
Functionality Before
Users receive unclear error messages like "Range error: Invalid string length" when
stringifyfailsFunctionality After
Users receive specific and clear error messages with advice so it is easy to understand and we are able to catch the errors in each bottleneck to make sense of the frequency of the bottlenecks.