Challenge LAB-0002
Map an Android bug report
Find your way around a bug report: its 22 categories, anchor sections, how far back event sections reach, and what a cut section does and does not tell you.
The task
An Android bug report is one zip file holding a dump of dozens of services and logs. It was written for developers, not for examiners, so its order follows the system and not your question. You will use the article's category map and the section matrix of five sample reports.
All challenge data is synthetic or comes from the Lab's published articles. No account is needed, nothing you type here leaves your browser except each answer you check, and the optional form if you send it.
What you need
Read and download
- Article LAB-0002: Android bug reports, category by category
- Dataset DS-0001: Samsung reset and recovery
- lab-0002-section-matrix.csv Figure 2: which sections are present, cut or absent in each of five reports
- lab-0002-category-map.json Figure 1: the 22 categories with anchor sections
Tools (all free)
- A plain text editor
- A spreadsheet or Python (to read the CSV and JSON files)
Any tool that reads text will do. You do not need the Lab's own software or an account.
Questions
Each answer is checked when you press Check answer, and you see the result straight away. A wrong answer costs nothing, and you may try again. A hint lowers the points you can earn for that question: 1, 2 and 3 points for hints 1, 2 and 3, and a correct answer always earns at least 1 point. Checking needs JavaScript; reading does not.
-
Need a hint?
Three hints, in order. Each one lowers the points you can earn for this question.
Hint 1 costs 1 point
The number is in the article's opening paragraph.
Hint 2 costs 2 points
It is also the number of rows in the table under Figure 1.
Hint 3 costs 3 points
More than twenty, fewer than twenty-five.
-
Need a hint?
Three hints, in order. Each one lowers the points you can earn for this question.
Hint 1 costs 1 point
Open the table under Figure 1 and find the category.
Hint 2 costs 2 points
Anchor sections are the names of services or logs, such as package or batterystats.
Hint 3 costs 3 points
The name is the short form of application operations.
-
Need a hint?
Three hints, in order. Each one lowers the points you can earn for this question.
Hint 1 costs 1 point
See Table 1, How far back each kind of section reaches.
Hint 2 costs 2 points
Event sections have short windows. A snapshot has none.
Hint 3 costs 3 points
The window differs between reports and is measured in minutes to hours.
-
Need a hint?
Three hints, in order. Each one lowers the points you can earn for this question.
Hint 1 costs 1 point
Use Figure 2, or the row Lock settings in the section matrix CSV.
Hint 2 costs 2 points
Count the reports marked present.
Hint 3 costs 3 points
The two Samsung reports and the Motorola report have it. The Huawei and Transsion-brand reports do not.
-
Need a hint?
Three hints, in order. Each one lowers the points you can earn for this question.
Hint 1 costs 1 point
See What a bug report cannot give.
Hint 2 costs 2 points
Three of the five options are things the report does not hold.
Hint 3 costs 3 points
It does not hold file contents and message bodies, network destinations, or ADB keys and signer certificates.
-
Need a hint?
Three hints, in order. Each one lowers the points you can earn for this question.
Hint 1 costs 1 point
Use the section matrix. Look at the column for the Motorola report.
Hint 2 costs 2 points
Both are rows under Differs by manufacturer or version.
Hint 3 costs 3 points
One is a vendor settings service, the other is an update component.
-
Need a hint?
Three hints, in order. Each one lowers the points you can earn for this question.
Hint 1 costs 1 point
The last two rows of the matrix give counts per report.
Hint 2 costs 2 points
Find the largest value in the row for sections cut by the time limit.
Hint 3 costs 3 points
It is one of the two Samsung reports.
-
Need a hint?
Three hints, in order. Each one lowers the points you can earn for this question.
Hint 1 costs 1 point
See the closing list in What a bug report cannot give.
Hint 2 costs 2 points
A cut section is not a clean one.
Hint 3 costs 3 points
It says what was not reached, and nothing about what happened there.
You have finished: what you should have learned
- Most of a bug report is a snapshot. Only a few sections hold a window of events, and the windows are short: minutes to hours for the system log, about a day for battery history.
- Core sections such as package, app ops, battery statistics and the system log were in all five sample reports. Vendor sections are not, and have no common layout.
- Count sections and read the end of large ones. A section cut by the device time limit means not captured, never nothing happened.
- Five reports are a handful, not a survey. State the sample when you say a section is or is not present.
Completion note
Typed here only. It appears on the printed note and is not saved or sent anywhere.
Optional: tell us a little about yourself
This helps the Lab see who the challenges reach. It is not needed to keep your points, and it is never linked to your answers. You can also use the stand-alone form at any time.
Thank you
Your answers were received.
Your id, kept in this browser. Write it down if you want to delete your answers from another device.