sweetpad icon indicating copy to clipboard operation
sweetpad copied to clipboard
verified publisher icon sweetpad-dev

Any plans to support test run?

Open rafaelpedretti-toast opened this issue 1 year ago • 12 comments

Hi

Are there plans to support tests via the extension, like showing/running via test explorer?

rafaelpedretti-toast avatar Jun 17 '24 14:06 rafaelpedretti-toast

Hello! Yes, tests are definitely on the to-do list. I think I can fairly easily add the "test" command to the context menu of the scheme on the "Build" panel to add basic support for running tests. However, later it should be rewritten to run and watch test statuses via "Test Explorer" using VScode Testing API.

hyzyla avatar Jun 17 '24 14:06 hyzyla

Maybe we should have a place to display the current to-do list. 😊

kkHAIKE avatar Sep 24 '24 12:09 kkHAIKE

@kkHAIKE nice idea!

hyzyla avatar Sep 24 '24 14:09 hyzyla

@kkHAIKE nice idea!

maybe readme will be a great place for todo list section

ahmed-ibrahim-salim avatar Oct 03 '24 10:10 ahmed-ibrahim-salim

@kkHAIKE @ahmed-ibrahim-salim here I've created todo list using "Projects" feature on Github https://github.com/orgs/sweetpad-dev/projects/2/views/1

I've never worked with "Projects" on GitHub, so I'm still getting used to it, but overall, I think I will add more tasks and prioritize them in the next few weeks

hyzyla avatar Oct 06 '24 13:10 hyzyla

I second this issue, this is the biggest pain point for using this extension for full-time iOS/macOS development. The fact that it can run the tests is fine but there is zero integration into the IDE other than the test log output.

cameroncooke avatar Oct 07 '24 15:10 cameroncooke

Hi! I've added basic support for running tests using Test Explorer. I would say it's in beta, and any feedback is welcome. It currently works only with XCTestCase classes and shows tests for the last opened file with tests. Configuration options like scheme, destination, and workspace path currently reuse the existing build configuration (I'm still not sure if this is the best option for running tests). Also, I recently noticed that tests for iOS don't show errors in stdout, unlike macOS, so currently only macOS supports inline error messages. For iOS, I'll need some time to figure out how to parse the .xcresult bundle to extract the error message.

CleanShot 2024-10-20 at 11 52 27@2x

CleanShot 2024-10-20 at 12 01 51@2x

hyzyla avatar Oct 20 '24 10:10 hyzyla

Thank you @hyzyla how can we test (excuse the pun) this out?

cameroncooke avatar Oct 20 '24 10:10 cameroncooke

Thank you @hyzyla how can we test (excuse the pun) this out?

  1. Update the extension from the marketplace (v0.1.38).
  2. Open the Swift file with tests using XCTestCase.
  3. Open the test explorer (the flask icon in your side panel).
  4. Click "Run test" on any individual test or the entire test suite

CleanShot 2024-10-20 at 12 43 42@2x

hyzyla avatar Oct 20 '24 10:10 hyzyla

Super interested in the part about parsing to get iOS test reported in tests explorer. Is there a way to help?

bitomule avatar Dec 03 '24 11:12 bitomule

@hyzyla I'm wondering, are there any plans to add test coverage support?

siddarthkalra avatar Jan 27 '25 14:01 siddarthkalra

As Tuist has the ability to cache test builds - i run tuist test but am struggling to get results back to Test Explorer. Is this possible?

grahamhindle avatar May 16 '25 09:05 grahamhindle