-
Notifications
You must be signed in to change notification settings - Fork 269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement testing framework #54
Comments
/bounty $150 |
💎 $250 bounty • CapSteps to solve:
Thank you for contributing to CapSoftware/Cap! Add a bounty • Share on socials
|
/attempt #54
|
/attempt #54 Options |
💡 @Mubashirshariq submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
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. |
/bounty $250 |
@richiemcilroy can you check the PR i have raised and let me know what changes needs to be done! |
@richiemcilroy We have to add tests in each of the apps in https://github.com/CapSoftware/Cap/tree/main/apps ? |
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).
The text was updated successfully, but these errors were encountered: