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

Add VSMobileCenterTest task #3349

Merged
merged 6 commits into from
Jan 5, 2017
Merged

Add VSMobileCenterTest task #3349

merged 6 commits into from
Jan 5, 2017

Conversation

yacaovsnc
Copy link
Member

No description provided.

Copy link
Contributor

@madhurig madhurig left a comment

Choose a reason for hiding this comment

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

Looks good, left some comments

"name": "VSMobileCenterTest",
"friendlyName": "Visual Studio Mobile Center Test",
"description": "Test mobile app packages with Visual Studio Mobile Center",
"helpMarkDown": "Test mobile app packages to Visual Studio Mobile Center",
Copy link
Contributor

Choose a reason for hiding this comment

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

Test mobile app packages with Visual Studio Mobile Center

"author": "Microsoft Corporation",
"version": {
"Major": 0,
"Minor": 111,
Copy link
Contributor

Choose a reason for hiding this comment

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

112?

"label": "Mobile Center Password",
"defaultValue": "",
"required": true,
"helpMarkDown": "Visit https://mobile.azure.com/settings/profile to set your password.",
Copy link
Contributor

Choose a reason for hiding this comment

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

Add a note here to use a secret build variable for the password. We have similar text in other tasks that you can follow.

"label": "DSym Directory",
"defaultValue": "",
"required": false,
"helpMarkDown": "Path to iOS symbol files"
Copy link
Contributor

Choose a reason for hiding this comment

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

End with .

"required": false,
"visibleRule": "locale = user",
"helpMarkDown": "Enter any two-letter ISO-639 language code along with any two-letter ISO 3166 country code in the format [language]_[country], such as en_US."
},
Copy link
Contributor

Choose a reason for hiding this comment

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

It would be better to keep this input next to "locale" since they are related.

Copy link
Member Author

Choose a reason for hiding this comment

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

Moved next to "locale"

"name": "framework",
"type": "pickList",
"label": "Test Framework",
"defaultValue": "appium",
Copy link
Contributor

Choose a reason for hiding this comment

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

Is "appium" the most popular or the first in alphabetical order? I would have picked "UI Test" since that is the type of test project created when a Xamarin project is created in VS.

Copy link
Member Author

Choose a reason for hiding this comment

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

I opted to keep it in alphabetical order so I don't play favoritism. :)

"defaultValue":"",
"visibleRule":"framework = appium",
"required": true,
"helpMarkDown":"Path to directory with Appium tests",
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we should use a period at the end of all the help markdown text

loggedIn = true;
}

// test prepare
Copy link
Contributor

Choose a reason for hiding this comment

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

My personal preference is to not do all the test runner setup ahead of time but set them up along the way. I feel it is more readable that way.

Copy link
Member Author

Choose a reason for hiding this comment

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

I agree in general. The reason I am trying to setup first here is we can do some basic input validation first just to make sure user doesn't need to wait a long time before an obvious error is encountered.

// logout
let logoutRunner = tl.tool(cliPath);
logoutRunner.arg(['logout', '--quiet']);
logoutRunner.exec();
Copy link
Contributor

Choose a reason for hiding this comment

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

shouldn't you await on logout?

Copy link
Member Author

Choose a reason for hiding this comment

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

sure, I will. This is clean up code so I didn't think we need to wait. However it's safer if we do.

@yacaovsnc yacaovsnc merged commit bd49b74 into master Jan 5, 2017
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