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

Investigate why testBundleDidFinish: never gets called

Open
#28 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
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
objective-c
Domain
mobile, testing

Research direction

Locate the testBundleDidFinish: callback and the test runner or harness that should invoke it. Reproduce a failing layout test, trace whether the callback is reached, and verify that the failure path is printed when the issue is fixed.

Written by the indexing model from the issue text.

Description

For some reason, this function never gets called which means it doesn't print out the path to test failures.

Dominant language
Objective-C
Stars
558
Forks
46
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 linkedin/LayoutTest-iOS

All issues in linkedin/LayoutTest-iOS

Similar issues

More Objective-C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.