Skip to content

Investigate length of E2E tests runs #64075

@ilonatommy

Description

@ilonatommy

On average, running our E2E tests takes order of magnitude of seconds. However, there are 2 tests that stand out and take order of magnitude of minutes, depending on the run even ~3min.

  • Microsoft.AspNetCore.Components.E2ETest.ServerExecutionTests.ServerVirtualizationTest.CanElevateEffectiveMaxItemCount_WhenOverscanExceedsMax
  • Microsoft.AspNetCore.Components.E2ETest.Tests.VirtualizationTest.CanElevateEffectiveMaxItemCount_WhenOverscanExceedsMax

This is a low priority job of investigating if there is anything in these tests that unnecessarily prolongs them and if we can do better.

Metadata

Metadata

Assignees

Labels

area-infrastructureIncludes: MSBuild projects/targets, build scripts, CI, Installers and shared frameworkclean-upThis issue is internal clean-up and has no effect on public APIs or expected behaviorstask

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions