Implement testing framework

[richiemcilroy]

Need to implement a testing framework for the various packages and apps in the monorepo.

Create one test example in each.

Must be easily scaleable to create other tests going forward.

Maybe research what is best for the desktop app (since it's a Rust powered Tauri app with Next.js on the frontend).

[richiemcilroy]

/bounty $150

[Mubashirshariq]

/attempt #54

Algora profile	Completed bounties	Tech	Active attempts	Options
@Mubashirshariq	1 bounty from 1 project	JavaScript, TypeScript, HTML		Cancel attempt

[dfordp]

/attempt #54

Options

• Cancel my attempt

[algora-pbc]

💡 @Mubashirshariq submitted a pull request that claims the bounty. You can visit your bounty board to reward.

[richiemcilroy]

Sorry for the slow progress here. Over the last couple of months we have completely redeveloped the app from the ground up, leading to the launch of Cap v0.3.0. It's a different architecture (Tauri v2 + SolidJS).

To complete this bounty, we'd need it to be implemented for the new architecture.

Needs to be as easy as possible to add new tests.

Please can you include a couple of example tests.

Upped the bounty to $250.

[richiemcilroy]

/bounty $250

[Mubashirshariq]

@richiemcilroy can you check the PR i have raised and let me know what changes needs to be done!

[Abiji-2020]

@richiemcilroy We have to add tests in each of the apps in https://github.com/CapSoftware/Cap/tree/main/apps ?
and any suggestion or idea of what are the frameworks should be used?

[promisingcoder]

/attempt #54

Options

• Cancel my attempt

[svperior-jon]

/attempt #54

I am taking a focused pass on the current Tauri v2 + SolidJS architecture. Plan:

• Wire existing desktop Vitest coverage into the root pnpm test Turbo pipeline.
• Add a package-level Vitest example for shared utilities so future package tests have a clear pattern.
• Keep this narrowly scoped to test infrastructure and meaningful example tests, then verify the changed workspaces locally.

AI-assisted with Codex; I will review the diff before opening the PR.

[JYZ-LESLIE]

/attempt #54\n\nI will ship a focused testing-framework bootstrap for desktop deeplink and parser flows with CI-ready structure, then follow up with incremental coverage PRs.

[NeurArk]

/attempt #54

I will take a differentiated pass from the current testing PRs: audit the existing desktop/utils coverage, then add a broader monorepo testing bootstrap with small example tests for additional apps/packages, shared Vitest conventions, and root/turbo scripts so future coverage is easy to extend.

I will avoid duplicating PR #1808 and only open a PR if the diff adds meaningful coverage beyond that scope. AI-assisted, manually reviewed before submission.

[zhengjynicolas]

/attempt #54

I am taking a narrow non-overlapping pass from PR #1808: add Vitest test scripts and small example tests for @cap/web-domain, @cap/sdk-embed, and @cap/sdk-recorder so package-level tests are easy to extend and run through the existing Turbo test pipeline. This intentionally avoids the desktop/utils scope already covered by #1808.