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

Test renaming an extension publisher/name #37155

Closed
2 tasks done
sandy081 opened this issue Oct 30, 2017 · 1 comment
Closed
2 tasks done

Test renaming an extension publisher/name #37155

sandy081 opened this issue Oct 30, 2017 · 1 comment

Comments

@sandy081
Copy link
Member

sandy081 commented Oct 30, 2017

Testing #34812

Complexity: 4

Note: Since renaming an extension needs support from Marketplace team, we will do a local rename here. It means doing following

  • Go to installed extensions folder
  • Open the package.json of the extension and rename the publisher / name.
  • Also change the folder name to match with above rename

You can also follow the above steps to change the version of the extension.

Test cases

An extension installed from Marketplace

  1. It should get synced with Marketplace, show latest data and updates if it has.
  2. Disable the extension (workspace/global does not matter)
  3. Rename the publisher of the extension as mentioned above.
  4. Disconnect from Internet to disconnect from Marketplace and Verify that extension is shown with renamed publisher and is disabled
  5. Connect to Marketplace and reload VS Code.
  6. It should get synced with Marketplace, show latest data and updates if it has.
  7. Extension should be disabled.

Recommendations and Dependencies

  1. Verify having an old extension name in workspace recommendations or dependencies is treated as unknown extension.

An extension installed as VSIX

  1. It does not get synced if there is no mapping extension in Marketplace
  2. It should get synced with Marketplace, show latest data and updates if there is a mapping extension in Marketplace.

Enablement / Disablement migration

  1. Open VS Code stable version pointing to a known extensions directory. Use --extensions-dir option.
  2. Install some extensions and disable some of them. (Global/Workspace does not matter)
  3. Open latest insiders on the same extensions directory
  4. Make sure extensions are disabled.
@vscodebot vscodebot bot added the extensions Issues concerning extensions label Oct 30, 2017
@sandy081 sandy081 added testplan-item and removed extensions Issues concerning extensions labels Oct 30, 2017
@sandy081 sandy081 assigned Tyriar and joaomoreno and unassigned Tyriar and joaomoreno Oct 30, 2017
@sandy081
Copy link
Member Author

@Tyriar assigning @joaomoreno as one of the testers of this.

@bpasero bpasero added this to the October 2017 milestone Oct 31, 2017
@jrieken jrieken self-assigned this Oct 31, 2017
@jrieken jrieken removed their assignment Oct 31, 2017
@joaomoreno joaomoreno removed their assignment Oct 31, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 15, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants