Skip to content

Reduce E2E test dependencies #27610

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.

Sign up for GitHub

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

Jump to bottom
Closed
4 tasks done
javiercn opened this issue Nov 7, 2020 · 3 comments
Closed
4 tasks done

Reduce E2E test dependencies #27610

javiercn opened this issue Nov 7, 2020 · 3 comments
Assignees
@javiercn
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework enhancement This issue represents an ask for new feature or an enhancement to an existing one severity-nice-to-have This label is used by an internal tool
Milestone
.NET 7 Planning

Comments

@javiercn
Copy link
Member

javiercn commented Nov 7, 2020 •
edited by TanayParikh
Loading

We currently use selenium for our E2E tests, which requires that we have the appropriate browsers installed as well as Java, NodeJS and yarn available on the machine.

Consider selenium alternatives that would allow us to remove these dependencies from the E2E test projects.
@javiercn javiercn added area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework enhancement This issue represents an ask for new feature or an enhancement to an existing one investigate labels Nov 7, 2020
@javiercn javiercn mentioned this issue Nov 7, 2020
Open
17 tasks
@javiercn javiercn self-assigned this Nov 7, 2020
@dougbu
Copy link
Contributor

dougbu commented Nov 18, 2020

Including this in the DoI project for discussion in that context

@JunTaoLuo JunTaoLuo added the severity-nice-to-have This label is used by an internal tool label Dec 16, 2020
@mkArtakMSFT mkArtakMSFT added this to the 6.0-preview2 milestone Jan 28, 2021
@javiercn javiercn mentioned this issue Feb 3, 2021
Merged
@javiercn javiercn removed their assignment Feb 16, 2021
@javiercn javiercn removed the Working label Feb 16, 2021
@ghost
Copy link

ghost commented Feb 18, 2021

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@javiercn javiercn mentioned this issue Apr 18, 2021
Closed
@javiercn javiercn modified the milestones: 6.0-preview6, 6.0-rc1 Jun 14, 2021
@mkArtakMSFT mkArtakMSFT modified the milestones: 6.0-rc1, 6.0.0 Jul 15, 2021
@mkArtakMSFT mkArtakMSFT modified the milestones: 6.0.0, .NET 7 Planning Oct 4, 2021
@TanayParikh TanayParikh mentioned this issue Oct 29, 2021
Closed
@TanayParikh
Copy link
Contributor

Given #37929 / #38344, I believe this is now done. Closing it out.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@javiercn javiercn

Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework enhancement This issue represents an ask for new feature or an enhancement to an existing one severity-nice-to-have This label is used by an internal tool
Projects
None yet
Milestone
.NET 7 Planning
Development

No branches or pull requests
6 participants
@SteveSandersonMS @JunTaoLuo @dougbu @javiercn @TanayParikh @mkArtakMSFT