Skip to content

Use NrpTeamAlias in Network's tests to set ownership #10233

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

Merged
merged 2 commits into from
Oct 15, 2019

Conversation

anton-evseev
Copy link
Contributor

@anton-evseev anton-evseev commented Oct 9, 2019

Description

Ensures that all Network tests use the same class to set test ownership

Checklist

  • I have read the Submitting Changes section of CONTRIBUTING.md
  • The title of the PR is clear and informative
  • The appropriate ChangeLog.md file(s) has been updated:
    • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
  • The PR does not introduce breaking changes
  • If applicable, the changes made in the PR have proper test coverage
  • For public API changes to cmdlets:
    • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
    • the markdown help files have been regenerated using the commands listed here

Comment on lines +52 to +54

// Azure NRP bastion dev team
public const string bastion = "bastion";
Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like bastion team is reorged to NRP dev team. Should it remove from Category?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think we can remove all NRP aliases from Category since they are duplicates (if you're okay with that)

Copy link
Contributor

Choose a reason for hiding this comment

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

Sure~I think you can remove them if there is not any reference any more.

Copy link
Contributor

@wyunchi-ms wyunchi-ms left a comment

Choose a reason for hiding this comment

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

I think you can remove them if there is not any reference any more.

@anton-evseev
Copy link
Contributor Author

Done, @wyunchi-ms, please take a look

Comment on lines -62 to -86
// Below is the list of aliases to contact on test behavior

// Virtual Appliance dev team
public const string nvadev = "nvadev";

// SDN NRP Dev Team
public const string sdnnrp = "sdnnrp";

// Pankaj's Team
public const string pgtm = "pgtm";

// Windows Azure SLB Dev Team
public const string slbdev = "slbdev";

// Brooklyn FTEs
public const string brooklynft = "brooklynft";

// Azure Network Analytics Dev Team
public const string netanalyticsdev = "netanalyticsdev";

// Windows Azure NRP dev team
public const string wanrpdev = "wanrpdev";

//Azure NRP Firewall dev team
public const string azurefirewall = "azurefirewall";
Copy link
Contributor

Choose a reason for hiding this comment

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

Hi @number213 are these variables also duplicated?

Copy link
Contributor

Choose a reason for hiding this comment

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

OK, there is not any reference of these variables in the code. They can be remove safely.

@wyunchi-ms wyunchi-ms merged commit f5bbf3d into Azure:network-october Oct 15, 2019
@anton-evseev anton-evseev deleted the nrp-team-alias branch October 15, 2019 23:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants