YDMmobile / oss
KOEN

Keyword / 19 entries

testing

이 키워드가 붙은 글입니다. 전체 글

Category
  1. 1

    Vitest Is Collecting Unrelated Tests? Start with the File List

    If Vitest reports a failure in a test file you do not recognize, inspect the file path before changing assertions, timeouts, or worker settings. A test collected from a tool's cache needs a different fix from a failing test in your application. The useful question is specific: which files did this invocation discover,…

    EN2026-10-23

  2. 2

    7 Silent Failures in My Flutter App That No Test Caught

    A token refresh that never ran, a crash filter that threw away crashes, and a test that defended a bug On 2026-10-03, four tests for a review screen in the Flutter app I maintain started failing. They couldn't find a snackbar. The snackbar was fine. The real error was this: The app decides whether it's running under…

    EN2026-10-21

  3. 3

    4 Things Claude Code Subagents Don't Inherit (and 1 Thing They Do)

    What I learned when my own subagents ignored my rules, skipped my gates, refused my approval, and read my answer key On 2026-10-02 I was testing a new Claude Code skill by running it through subagent scenarios. One of the subagents did exactly what the skill told it to do: it stopped at the plan-approval gate, showed…

    EN2026-10-20

  4. 4

    7 Flutter App Patterns Worth Copying Into Your Next App

    What a survey of my Riverpod + go_router app says to keep, and what to fix before you paste it My test harness has a doc comment that says (in Korean) it initializes ProviderScope, ScreenUtilInit and EasyLocalization. It does not wrap anything in EasyLocalization. Screen tests that use it had been running without…

    EN2026-10-19

  5. 5

    The Export Line Was Not the Documentation

    I found the symbol in one search. That line looked generous. It gave me the function name. It showed two arguments. It even showed that the options object and status both have defaults. I could have written the documentation immediately. I would have documented the shape and guessed the behavior. The export line…

    EN2026-10-08

  6. 6

    0 warnings는 아무것도 컴파일하지 않았다는 뜻일 수 있다

    build가 성공했다. warning은 0건이었다. 기분 좋게 “warning 없음”이라고 적을 뻔했다. 그런데 compiler가 대상 Swift file을 읽지 않았다. incremental build가 모든 것을 up-to-date로 판단했다. 0은 code의 상태가 아니었다. 이번 build가 수행한 compiler work의 상태였다. compiler warning을 관찰하려면 compiler가 source를 읽어야 한다. incremental build는 바뀌지 않았다고 판단한 work를 건너뛸 수 있다. 그 경로에서는 이전 compile에서 보였던…

    KO2026-10-07

  7. 7

    The Number I Wrote Down Was Not Evidence

    I had a test count I trusted. It was 245. Another method returned 269. I explained the larger number away. The text counter must have overcounted parameterized tests, I wrote. Then I opened the result bundle. It reported 269 distinct test identifiers. Forty-one of those nodes carried parameter arguments. The bundle…

    EN2026-10-06

  8. 8

    The Widget Had the Right Width Factor and Rendered at 702 x 0

    The progress fill had widthFactor: 1.0. The widget test found it and confirmed the property. The full button remained tappable. The fill was also invisible. Flutter had laid it out at Size(702, 0). Technically, it occupied the full available width. It just did so with the vertical presence of a very committed line of…

    EN2026-10-01

  9. 9

    The Mobile Screenshot Was 390 Pixels Wide and Still Lied About the Viewport

    A 390-pixel-wide capture showed horizontal overflow. The visual review appeared to have found a mobile layout bug. Except it had not. Headless Chrome had kept an approximately 500-pixel layout viewport and cropped the image to 390 pixels. The screenshot dimensions were correct. The page geometry behind them was not.…

    EN2026-09-29

  10. 10

    The Phone Was Not My Test Rig. It Was Already in Use

    I was already using my phone for development when an automated session prepared another iOS performance run against it. A screenshot exposed the collision before the second run took control. That should have ended the attempt. The automation also sent a mouse click intended for the app. It landed on a different window…

    EN2026-09-29

  11. 11

    빈 화면 테스트는 검증이 아닙니다: 원하는 상태를 먼저 만들어야 합니다

    앱을 실행했습니다. 스크린샷을 찍었습니다. 화면은 멀쩡했습니다. 그런데 확인하려던 던전 보드, 마감 임박 표시, 위젯 완료 상태는 하나도 없었습니다. 무엇을 검증한 걸까요? 음. 앱이 빈 상태를 잘 보여준다는 사실은 검증했습니다. 그것도 꽤 중요할 수 있습니다. 하지만 채우고 싶었던 상태를 만들지 못했다면, 그 스크린샷은 다른 질문에 대한 답입니다. 스크린샷 도구가 있다고 해서 원하는 화면까지 자동으로 도착하는 것은 아닙니다. (이동 기능이 없으면 관광도 못 합니다.) 테스트나 스크린샷은 마법 카메라가 아닙니다. 어떤 상태를 만들고, 그 상태를 도구가 읽고,…

    KO2026-09-23

  12. 12

    A Lint Rule That Matches Nothing Is Not Green

    A custom lint rule can compile, execute, report zero diagnostics, and be completely broken. That is the unpleasant lesson behind many static-analysis migrations. A removed API causes a useful red build. The obvious repair makes the project compile again. Then a changed query, stale type name, or weakened library check…

    EN2026-09-15