Do Bugs Speak?
Do bugs speak?
Yes, they do. People speak different languages like English, German, French, Chinese etc. But is communication to bugs possible? It is important to understand them, because they really tell us something. There is valuable information underlying the defects of a software, and information mining from defects promises for improvements in terms of quality, time, effort and cost.
Problem Definition
A comprehensive analysis on all created defects can provide precious insights about the product. For instance; if we notice that a bunch of defects heap together on a feature, we can conclude that the feature should be investigated and cured. Or we can make some observations about the severity or assignee of similar defects. Therefore, there are some potential patterns to be discovered under defects.
Wrap-up
Defect analysis is very important for QA people, and especially for QA managers. We utilize lots of aspects to get an idea about the product itself or our procedures. For instance while monitoring defect distribution across testing types, we will discuss how to get an idea about the quality of our testing approach. I.e whether we are applying all types in a balanced way. (functional, performance, documentation, etc.) Or over another graph, in which we track the gap between open defects and resolved defects, we will discuss what action items we can take when the gap widens. Finally, with ML assistance, we will see how we can reduce manual effort and cost.
Results & Conclusion
In this session, we discuss data mining from bugs and usage of ML in defect management. Objective of the study is:
- To present in which ways defects can be analyzed
- To present how ML can be used to make observations over defects
- To provide empirical information supporting (b)
Outline/Structure of the Talk
* How to learn from bugs
* Metrics to learn from bugs
* Ways to collect metrics
Learning Outcome
Lessons Learned
After all the experience I have had to build a successful bug management process, I had insights about the most critical parts of building such as lifecycle:
- What kind of environment we should build to be able to extract hidden patterns and valuable information from defects.
- What kind of monitoring ways can be used to make the status visible in the most possible way. (Various pie charts, bar graphs and tables will be shown to demonstrate distribution of defects across different aspects. )
- What can be the valuable information in each monitoring activity.
- How can we classify/cluster defects using NLP techniques over various algorithms (including SVM, Decision Trees, Ensemble Methods) with benchmarking and results (accuracy rates).
The presentation aims to help also to attendees in terms of:
- Mine valuable data from defects
- Get insights about test cycles
- Reduce defect assignment errors
- Perform correct defect triage
Target Audience
Testers, PO, Developers
Links
https://www.mesutdurukal.com/conferences.html
schedule Submitted 1 year ago
Recent Activities
- description Yasunobu Kawaguchi updated proposal Do Bugs Speak?schedule 7 months ago
- description Kenta Sasa updated proposal Do Bugs Speak?schedule 11 months ago
- description Yasunobu Kawaguchi updated proposal Do Bugs Speak?schedule 1 year ago
Call for Proposals CLOSED
Ended on Mar 3 '22 01:00 PM JST
Call for Speakers 登壇者の募集
セッションのスピーカーを募集します。DevOpsに関わる技術やケーススタディ、組織内の活動、組織外のコミュニティ活動など、幅広いセッションのご提案をお待ちしております。
We’re looking for a mix of technical and cultural talks that relate to the central conference themes.
Deadline for posting : 1 pm on Mar 3th (JST: UTC+9)
投稿の締切: 3月3日13:00 (日本時間）
※3月1日の締切日にサービストラブルがありましたので、影響を考慮し締切を3月3日13:00（日本時間）に延長しました
Session Type / セッション・タイプ
2つのタイプのセッションがあります。
- レギュラー・トーク：フル（45分）かハーフ（20分）のいずれかになります。
- ライトニング・トーク：ライトンニング・トークのセッションタイム中におこなわれます。各5分のスロットとなります。
There are two types of sessions planned:
- Regular talk; these will be either full- (45 minute) or half-length (20 minutes) talks.
- Lightning talk; these are presented in during a lightning talk session. They are 5-minute slots.
Session Categories / セッション・カテゴリー
- how-to-begin-devops：はじめの一歩
- infrastructure-as-code：インフラ自動化(IaC)
- agile-testing：アジャイルテスティング
- quality-engineering：品質エンジニアリング
- customer-success：カスタマーサクセス
- thoughts-and-experiments：新しい提案や実験
- continuous-delivery：継続的デリバリー
- administration-and-security：インフラ管理とセキュリティ
- low-code-no-code：ローコード、ノーコード
- collaboration-of-organizations：組織間のコラボレーション
- microservice-and-containers：マイクロサービスとコンテナ技術
- serverless-computing：サーバーレス・コンピューティング
- logging-monitoring：ログとモニタリング
- testing-in-production：本番環境でのテスト
- metrics-and-management：メトリクスとマネジメント
Language / 言語
日本語がメインの言語となりますが、半分ほどのトークは英語でおこなわれる予定です。
英語でのトークをご希望の場合は使用するスライドを事前にご提出下さい。同時通訳の事前準備に利用致します。日本語を話されない方も、事前にご本人の日本語レベルをお知らせ下さい。
Although Japanese will be the primary language of the conference, we’re striving for about half of the talks to be in English.
If you’re planning on submitting an English talk, please note that it will be very important to prepare the slides well in advance, so that we can prepare for simultaneous translation. While you won’t be required to speak or understand Japanese, please note your Japanese language-level.
kyon _mm
Yotaro Takahashi
Satoshi Yokota
Tadahiro Yasuda
Yotaro Sato
