Skip to content

Add ai agent skill for iOS instrumented tests#2847

Open
ASalavei wants to merge 2 commits intojb-mainfrom
andrei.salavei/ios-instrumented-test-skill
Open

Add ai agent skill for iOS instrumented tests#2847
ASalavei wants to merge 2 commits intojb-mainfrom
andrei.salavei/ios-instrumented-test-skill

Conversation

@ASalavei
Copy link

Add claude skill explaining how to run iOS Instrumented Tests

Release Notes

N/A

@ASalavei ASalavei changed the title Add claude skill for iOS instrumented tests Add ai skill for iOS instrumented tests Mar 11, 2026
@ASalavei ASalavei changed the title Add ai skill for iOS instrumented tests Add ai agent skill for iOS instrumented tests Mar 11, 2026
@@ -0,0 +1,39 @@
---
name: ios-instrumented-tests
Copy link
Collaborator

@igordmn igordmn Mar 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This duplicates and extends the "Run iOS instrumented tests" in MULTIPLATFORM.md, and seems useful for humans too?

Can we just move all this there, and point agents to the readme?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean, to use MULTIPLATFORM.md instead of skills - not sure it's a good idea. At least it goes against the documentation. Skills have very specific format and dedication. If you want the agent to do tasks efficiently, you should follow this guidelines.
Obviously, we can tell the LLM to read MULTIPLATFORM.md before doing any job, but it won't be the same.
I would say, vice versa it does not work either because skills will have things like This skill should be used when the user asks about "running iOS tests", "iOS instrumented tests", "how to run ios tests", "launch specific ios test" and these tests are located in the "compose/ui/ui/src/uikitInstrumentedTest" directory. which does not look good for human-readable manual

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What I am worried about:

  • we described useful information for humans that we didn't describe in MULTIPLATFORM.md:
    • that I need to change "compose/ui/ui/src/uikitInstrumentedTest/kotlin/androidx/compose/ui/Configuration.kt" to run specific tests
    • we mentioned simulator id, do we need to specify it? we didn't mention it in MULTIPLATFORM.md
    • the purpose of testutils-xctest
    • where the uikitInstrumentedTest environment is located (compose/ui/ui/src/uikitInstrumentedTest/kotlin/androidx/compose/ui/test)
  • we duplicated information and we have to keep 2 places up-to-date

Maybe we can solve it this way:

  • move all human-useful info to MULTIPLATFORM.md, testutils-xctest/README.md, ui/ui/src/uikitInstrumentedTest/README.md
  • keep robot-specific info here and reference human-related-docs
  • remove some info that isn't useful for humans and robots can easily know this.
  • avoid specific names/paths to not miss them during refactorings ("the setup function" instead of "setupXCTestSuite", "the xc test configuration Kotlin file" instead of the specific file)

Though, if you think it could degrade performance of the agent, we can accept the new duty of keeping this up-to-date.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you have doubts, another opinion, or it is more difficult to implement, I am fine just with the current skill

@ASalavei ASalavei requested a review from igordmn March 11, 2026 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants