Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Classical and detail header: test follow-ups

Open
#1,076 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
mobile, testing

Research direction

Read the context in #1065 and #1068, then locate the phone-album-detail-short-window screenshot test and the Maestro flow for Pink Floyd Now Playing; the scratch flows are under the owner-specific path in the issue. First check whether the short-window test fails with the old boundsInWindow code, then run the flows on a device with suitable test media. Done means the regression is reproduced and the non-classical album and shared-work sheet checks are captured.

Written by the indexing model from the issue text.

Description

later

Loose ends from the #1065 real-album screenshot run and the #1068 header fix.

  • #1068 short-window test: the new phone-album-detail-short-window screenshot (300dp height) probably doesn't reproduce the bug it guards, where boundsInWindow clipping marked the page collapsed at scroll 0. Use about 200dp or fontScale 2f, and check that the test fails against the old boundsInWindow code.
  • Pink Floyd Now Playing: the Maestro flow that plays Atom Heart Mother and screenshots Now Playing failed, cause not investigated. The check is that a non-classical album shows no work ribbon. The album page itself was right (no work blocks).
  • "Other recordings": untested on a device. None of the real test albums share a work, so the sheet never appeared. Add a second recording of a work that's already in the set (e.g. another Beethoven 5) to the test media and capture the sheet.

Scratch flows: /Users/tim/s2-scratch/classical/flows/ (owner's Mac).

Dominant language
Kotlin
Stars
231
Forks
28
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from timusus/Shuttle2

All issues in timusus/Shuttle2

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.