-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Any plans to support test run? #19
Comments
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. |
Maybe we should have a place to display the current to-do list. 😊 |
@kkHAIKE nice idea! |
maybe readme will be a great place for todo list section |
@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 |
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. |
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. |
Thank you @hyzyla how can we test (excuse the pun) this out? |
|
Super interested in the part about parsing to get iOS test reported in tests explorer. Is there a way to help? |
Hi
Are there plans to support tests via the extension, like showing/running via test explorer?
The text was updated successfully, but these errors were encountered: