MobileNativeFoundation / MobileNativeFoundation/XCLogParser

Cannot get unit tests stats due to missing test logs either in derived data or result bundle path

Open
#127 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
1.9k
Forks
138
PR merge metrics
No merged PRs in 30d

Description

I'd like to gather the test coverage statistics for a given target in a project. The Xcode version that I use is 12.4. I did run tests for a project via xcodebuild command:

$ xcodebuild test -scheme Demo -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 11 Pro,OS=14.4' -resultBundlePath ~/Demo/result

According to the blog post mentioned in the README file, there should be .xcactivitylog log generated at the result bundle path, however, with Xcode 12.4, it is not. There's a .xcresult file instead.

I also checked the derived data and same results.

I tried to simply parse the build activity log, but no data about unit tests has been found:

$ xclogparser parse --project Demo --reporter html

Could you please help me to figure out the way to get the unit tests coverage stats? 🙏

I will gladly update the documentation if needed 😊

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.

Research direction

Start with the README's test-logs section and reproduce the reported xcodebuild command using Xcode 12.4. Compare the generated .xcresult bundle with the expected .xcactivitylog inputs and inspect the parse command's available handling for each; done means documenting a working coverage-statistics path or clearly recording the limitation.

Written by the indexing model from the issue text.

Assessment

Domain
cli, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.