Skip to content
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

Native mobile app testing #227

Closed
slavingia opened this issue Dec 31, 2024 · 13 comments
Closed

Native mobile app testing #227

slavingia opened this issue Dec 31, 2024 · 13 comments

Comments

@slavingia
Copy link
Contributor

What

  • Native mobile app testing support in Shortest for iOS and Android.
  • Core workflows to install, launch, and interact with real/emulated apps using Shortest’s plain-English test syntax.
  • Additional setup docs or scripts to simplify environment configuration for mobile testing.

Why

  • Users need the same straightforward, AI-assisted test coverage for native mobile apps that Shortest offers for web.
  • Reduces QA overhead by allowing devs to reuse the existing Shortest approach (plain English tests) across all platforms.
  • Unlocks the $2,000 bounty for the first contributor to implement iOS + Android support, payable in cash, Anti-Work (Gumroad, Inc.) equity, or a combo.
@gladyshcodes

This comment was marked as off-topic.

@slavingia
Copy link
Contributor Author

Why? I think one repo is much less cognitive load and seems reasonable to have it be able to test all 3 platforms using computer use.

@gladyshcodes

This comment was marked as off-topic.

@slavingia
Copy link
Contributor Author

Yeah not sure the approach but something like that for sure will be useful.

@crmchattie
Copy link

Is someone/are people actively working on this? I'm interested in helping out. If not, I will start.

@rmarescu
Copy link
Member

@gladyshcodes has a draft PR #260. Probalby best to collaborate on that one, to reduce duplicate effort.

@rmarescu rmarescu moved this to In Progress in Shortest Jan 19, 2025
@rmarescu rmarescu linked a pull request Jan 19, 2025 that will close this issue
@gladyshcodes

This comment was marked as off-topic.

@rmarescu
Copy link
Member

I think we can discuss technical details next week, and scope for best approach. For now, we should pause development on this until we have a better foundation in place.

@gladyshcodes

This comment was marked as off-topic.

@crabest
Copy link
Contributor

crabest commented Jan 28, 2025

instead of another repo, wouldn't be better to have a seperated folder for mobile with its core functions just my draft https://github.com/anti-work/shortest/pull/230/files ?

Image

@gladyshcodes

This comment was marked as off-topic.

@gladyshcodes

This comment was marked as off-topic.

@rmarescu rmarescu moved this from In Progress to Scoping needed in Shortest Jan 31, 2025
@rmarescu rmarescu added this to the v0.4.5 milestone Feb 3, 2025
@rmarescu rmarescu removed this from the v0.4.5 milestone Feb 23, 2025
@rmarescu
Copy link
Member

Not a priority right now, will reopen then time comes.

@rmarescu rmarescu closed this as not planned Won't fix, can't repro, duplicate, stale Feb 26, 2025
@github-project-automation github-project-automation bot moved this from Scoping needed to Done in Shortest Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants