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

Add tests for `logError` thread-safety / Make it return a value

Open
  • Is something wrong?
#259 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
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
swift
Domain
mobile-dev, testing

Research direction

Start with the commented usage in Tests/Tests/CrashLoggingTests.swift, lines 97–114, and read the referenced WordPress iOS discussion for the intended behavior. Determine the expected thread-safety coverage and return value before changing anything; done means those expectations are captured by tests and the requested behavior is verified.

Written by the indexing model from the issue text.

Description

See @salimbraksa's comment from Jetpack and WordPress iOS: https://github.com/wordpress-mobile/WordPress-iOS/pull/20846/files#r1231271865

I could only find one usage of logError in the tests, and is commented:

https://github.com/Automattic/Automattic-Tracks-iOS/blob/01e73975896fd63ada5b992a2dcc3acd55f90253/Tests/Tests/CrashLoggingTests.swift#L97-L114

Dominant language
Swift
Stars
47
Forks
15
Avg merge
1d 34m
Merged PRs (30d)
1

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 Automattic/Automattic-Tracks-iOS

All issues in Automattic/Automattic-Tracks-iOS

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.