npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@kaizenreport/kensho-xcuitest

v0.1.1

Published

Kensho adapter for XCUITest — converts an .xcresult bundle from `xcodebuild test` into kensho-results/ via xcrun xcresulttool.

Downloads

28

Readme

@kaizenreport/kensho-xcuitest

Kensho adapter for native iOS XCUITest — converts an .xcresult bundle from xcodebuild test into kensho-results/ so the Kensho CLI can build a static report.

Platform requirement

.xcresult bundles are an Apple-proprietary format. Parsing them requires macOS + Xcode Command Line Tools (the xcrun xcresulttool binary).

For non-mac CI runners, generate the JSON dump on the mac side once and ship it through:

# on macOS:
xcrun xcresulttool get --format json --path ./out.xcresult > out.xcresult.json
# anywhere:
npx kensho-xcuitest --input out.xcresult.json --output kensho-results

Install

pnpm add -D @kaizenreport/kensho-xcuitest @kaizenreport/kensho

Use

xcodebuild -scheme AcmeUITests \
           -destination 'platform=iOS Simulator,name=iPhone 15,OS=17.4' \
           test -resultBundlePath ./out.xcresult

npx kensho-xcuitest --input ./out.xcresult --output ./kensho-results
npx kensho validate ./kensho-results
npx kensho generate --input ./kensho-results --output ./kensho-report
npx kensho open --report ./kensho-report

What gets captured

| xcresulttool field | Kensho field | | -------------------------------------------------------- | ----------------------------------- | | ActionTestSummary.name | case.name | | ActionTestSummary.identifier + parent group names | case.fullName / case.suite[] | | documentLocationInCreatingWorkspace.url | case.filePath + case.line | | testStatus (Success/Failure/ExpectedFailure/Skipped) | case.status (pass/fail/broken/skip) | | duration (seconds) | case.duration (ms) | | activitySummaries[] (recursive) | case.steps[] (with sub-steps) | | activitySummaries[].attachments[] | case.steps[].attachments[] | | failureSummaries[] | case.errors[] | | runDestination.targetDeviceRecord.modelName | run.env.device | | runDestination.targetDeviceRecord.operatingSystemVersion | run.env.osVersion | | testableSummaries[].targetName | case.labels.target |

framework.name = 'xcuitest'. Status mapping:

  • Successpass
  • Failurefail
  • ExpectedFailurebroken
  • Skippedskip

Notes on attachments

Real .xcresult bundles store screenshots/videos inside the bundle as referenced blobs. The adapter calls xcrun xcresulttool export --type file --id <ref> to pull each one out into kensho-results/attachments/<caseId>/.

When running on a fixture JSON dump (no real bundle next to it), the adapter writes a small placeholder file so the case still references something — the schema requires relativePath to point at a file on disk.