Skip to content

Add release gate tests for activation time #12645

Closed as not planned
Closed as not planned

Description

We should have some tests before we release to ensure we have not regressed significantly on activation.

Activity

  1. DonJayamanne commented on Jun 29, 2020

    @DonJayamanne

    We had this issue in the past (activation times got worse) and we added the following smoke test:

    • Test activation of current VSIX (i think we loaded it 5 times or so)
    • Download and test activation of latest VSIX in marketplace (exact same test, but different VSIX)

    Compare the two activation times.

    • This doesn't compare activation times overt time
    • This merely tests activation isn't worse than what is in marketplace
    • The benefit was we were kinda comparing apples with apples, VSIX on same machine (ignoring varying stress/loads on machine at any given point in time)

    We removed this test some time ago, can't remember why.

  2. ghost removed
    triage-neededNeeds assignment to the proper sub-team
    on Jun 30, 2020
  3. added
    needs spikeLabel for issues that need investigation before they can be worked on.
    and removed
    needs proposalNeed to make some design decisions
    on Aug 12, 2020
  4. karrtikr commented on Dec 22, 2022

    @karrtikr

    See #2853 for ideas.

  5. removed
    needs spikeLabel for issues that need investigation before they can be worked on.
    on Dec 18, 2023
  6. locked as resolved and limited conversation to collaborators on Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-internalLabel for non-user facing issuesfeature-requestRequest for new features or functionality

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions