The document discusses methods for error handling and crash reporting in software development, emphasizing the use of a bugsnag client to capture exceptions and notify through a specific error notification workflow. It mentions the importance of reproducing crashes, defensive programming, and a structured approach to rolling out beta versions. Additionally, it contains code snippets demonstrating testing procedures for handling tips in a sales history context.

1. Crash Fast
&
Furious
Pierre-Yves Ricau, Square

3. Source: https://t.co/uH1EqxqAow

8. 1
2

9. 1
2
3

10. 1
2
3
4

12. 1
2

14. public void uncaughtException(Thread t, Throwable e) {
bugsnagClient.notify(e, Severity.ERROR);
originalHandler.uncaughtException(t, e);
}

15. private void notify(Throwable exception, Severity severity) {
final Error error = new Error(config, exception);
error.setSeverity(severity);
captureState(error);
Async.run(new Runnable() {
@Override
public void run() {
deliver(error);
}
});
}

16. Crashs natifs
1
2

20. Reproduire

26. 1
2
3
4

28. Infos statiques

31. 1
2
3

33. Rolling log
1
2

37. squ.re/leakcanary

40. Defensive programming

41. Offensive programming
Crash Fast
2
1

42. Exception Grouping

43. 1
2

45. @Test public void submitTipSuccess() {
withRobot(SalesHistoryScreenRobot.class) //
.selectFirstBillAwaitingTipWithAmount(500_00L) //
.enterCustomTip("100") //
.clickSettleCustomTip() //
.checkSettleTipButtonConfirmAmount("$501.00") //
.clickSettleCustomTip();
}

47. Dogfood / Beta

48. Staged Rollout

51. • Process process process
• Repro repro repro
• Crash Fast & Furious

52. @Piwai