Artwork

Nội dung được cung cấp bởi iteration podcast, John Jacob, and JP Sio - Web Developers. Tất cả nội dung podcast bao gồm các tập, đồ họa và mô tả podcast đều được iteration podcast, John Jacob, and JP Sio - Web Developers hoặc đối tác nền tảng podcast của họ tải lên và cung cấp trực tiếp. Nếu bạn cho rằng ai đó đang sử dụng tác phẩm có bản quyền của bạn mà không có sự cho phép của bạn, bạn có thể làm theo quy trình được nêu ở đây https://vi.player.fm/legal.
Player FM - Ứng dụng Podcast
Chuyển sang chế độ ngoại tuyến với ứng dụng Player FM !

❌ Extreme Testing

37:19
 
Chia sẻ
 

Manage episode 243311288 series 1900125
Nội dung được cung cấp bởi iteration podcast, John Jacob, and JP Sio - Web Developers. Tất cả nội dung podcast bao gồm các tập, đồ họa và mô tả podcast đều được iteration podcast, John Jacob, and JP Sio - Web Developers hoặc đối tác nền tảng podcast của họ tải lên và cung cấp trực tiếp. Nếu bạn cho rằng ai đó đang sử dụng tác phẩm có bản quyền của bạn mà không có sự cho phép của bạn, bạn có thể làm theo quy trình được nêu ở đây https://vi.player.fm/legal.

Iteration — A weekly podcast about programming, development, and design through the lens of amazing books, chapter-by-chapter.

This episode uses Chapter 13 of Extreme programing as a jumping off point

Testing Early, Often, and Automated

Here is the dilemma in software development: defects are expensive, but eliminating defects is also expensive.

  • Instead of talking about having a kick-ass automated test suite, frequently testing code, and all of that good stuff, we should talk about something a little different.

Q: What was the last big bug you can think of? How did you handle it?

  • Health coaching group discussions, mobile users could not post into group discussions for 48 hours. It’s a core feature of the platform.
  • React Native Upgrade → Weird android bug where people could not take a photo to upload their proof of funds

Q: What was the reason for the latest big bug?

  • lack of automated integration tests in the Mobile app.
  • We have some unit testing we also have full API tests, but not enough coverage in the integration.
  • We made a small change to the group discussion model, the mobile app wasn’t updated to consider this change, timing the rollout.
  • Android Weirdness, lack of QA, rushing to get to the latest and greatest

Q: How do you handle bugs in general?

  • Testing is first line of defense.
  • QA is backup (One other dev)
  • App signal is the catch all (After deployment)
  • Users are the last line of defense RABBITHOLE
    • Give users a clear escape hatch / line of communication.
    • So many times we’ve caught flawed design assumptions from that feedback. Users love it too.
    • Superlative language "Thank you so much, you are the best, we really really appreciate you sending that in and I'm so sorry if you are having issues. "

Q: John Ask: What’s the most common causes of bugs?

  • Test data does not properly represent production data - phone formats / etc
  • An Edge case that wasn’t considered
  • The feature functions properly but the functionality is wrong / not what the stakeholder intended.
  • Rollout was not planned, data transition or all platforms are not in sync.
  • Browser or context considerations. Mobile vs tablet / android device universe.
  • Lack of QA, lack of tests
  • Rushing things

John — Summary / Thoughts on book overall

  • Overall got the most out of this vs other books we've read

Picks

  • JP: Heroku! Review Apps (spins up a new app every time a PR is opened); Pipelines
  • John: Contentful + Rails to give clients ability to update copy and images on marketing pages.
  continue reading

78 tập

Artwork

❌ Extreme Testing

iteration

113 subscribers

published

iconChia sẻ
 
Manage episode 243311288 series 1900125
Nội dung được cung cấp bởi iteration podcast, John Jacob, and JP Sio - Web Developers. Tất cả nội dung podcast bao gồm các tập, đồ họa và mô tả podcast đều được iteration podcast, John Jacob, and JP Sio - Web Developers hoặc đối tác nền tảng podcast của họ tải lên và cung cấp trực tiếp. Nếu bạn cho rằng ai đó đang sử dụng tác phẩm có bản quyền của bạn mà không có sự cho phép của bạn, bạn có thể làm theo quy trình được nêu ở đây https://vi.player.fm/legal.

Iteration — A weekly podcast about programming, development, and design through the lens of amazing books, chapter-by-chapter.

This episode uses Chapter 13 of Extreme programing as a jumping off point

Testing Early, Often, and Automated

Here is the dilemma in software development: defects are expensive, but eliminating defects is also expensive.

  • Instead of talking about having a kick-ass automated test suite, frequently testing code, and all of that good stuff, we should talk about something a little different.

Q: What was the last big bug you can think of? How did you handle it?

  • Health coaching group discussions, mobile users could not post into group discussions for 48 hours. It’s a core feature of the platform.
  • React Native Upgrade → Weird android bug where people could not take a photo to upload their proof of funds

Q: What was the reason for the latest big bug?

  • lack of automated integration tests in the Mobile app.
  • We have some unit testing we also have full API tests, but not enough coverage in the integration.
  • We made a small change to the group discussion model, the mobile app wasn’t updated to consider this change, timing the rollout.
  • Android Weirdness, lack of QA, rushing to get to the latest and greatest

Q: How do you handle bugs in general?

  • Testing is first line of defense.
  • QA is backup (One other dev)
  • App signal is the catch all (After deployment)
  • Users are the last line of defense RABBITHOLE
    • Give users a clear escape hatch / line of communication.
    • So many times we’ve caught flawed design assumptions from that feedback. Users love it too.
    • Superlative language "Thank you so much, you are the best, we really really appreciate you sending that in and I'm so sorry if you are having issues. "

Q: John Ask: What’s the most common causes of bugs?

  • Test data does not properly represent production data - phone formats / etc
  • An Edge case that wasn’t considered
  • The feature functions properly but the functionality is wrong / not what the stakeholder intended.
  • Rollout was not planned, data transition or all platforms are not in sync.
  • Browser or context considerations. Mobile vs tablet / android device universe.
  • Lack of QA, lack of tests
  • Rushing things

John — Summary / Thoughts on book overall

  • Overall got the most out of this vs other books we've read

Picks

  • JP: Heroku! Review Apps (spins up a new app every time a PR is opened); Pipelines
  • John: Contentful + Rails to give clients ability to update copy and images on marketing pages.
  continue reading

78 tập

Tất cả các tập

×
 
Loading …

Chào mừng bạn đến với Player FM!

Player FM đang quét trang web để tìm các podcast chất lượng cao cho bạn thưởng thức ngay bây giờ. Đây là ứng dụng podcast tốt nhất và hoạt động trên Android, iPhone và web. Đăng ký để đồng bộ các theo dõi trên tất cả thiết bị.

 

Hướng dẫn sử dụng nhanh

Nghe chương trình này trong khi bạn khám phá
Nghe