Skip to content

Conversation

@tsuemura
Copy link

We have no integration test with --device-ids option for autify mobile link start commmand. This PR add the integration test and the network recording file.

This test is also required for the Bitrise step autifyhq/bitrise-step-autify-test-run#12.

Copy link
Contributor

@xiankai xiankai left a comment

Choose a reason for hiding this comment

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

small reminder: need to fix lint as well

"https://mobile-app.autify.com/projects/4yyFEL/test_plans/1EtZ0P";
const mobileWorkspaceId = "4yyFEL";
const mobileAndroidBuildId = "d1ulrD";
const mobileDeviceIds = "R5CY23ND1KE";
Copy link
Contributor

Choose a reason for hiding this comment

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

out of curiosity how did you arrive at this value? is it like your own device ID that you'll keep on during tests or something like a mock value?

Copy link
Author

Choose a reason for hiding this comment

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

This is my own device ID value. This device ID should be in the "autify-cli" project so that we can record the actual API response. It means, if someone wants to update the recorded response, they will need to set their own local device temporarily :(

Copy link
Contributor

@xiankai xiankai Oct 16, 2025

Choose a reason for hiding this comment

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

I see, I guess it's unavoidable but at least having a one-line comment that this value needs to be replaced if we want to run any local device tests would help

Copy link
Contributor

@xiankai xiankai left a comment

Choose a reason for hiding this comment

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

I understand why we need the test here now

ref

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