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

Feature: add a UI test project to solution #300

Open
mrlacey opened this Issue May 11, 2017 · 7 comments

Comments

Projects
None yet
4 participants
@mrlacey
Collaborator

mrlacey commented May 11, 2017

Add a UI test project to the solution.

This should include a test to launch the app and take a screenshot.

@mrlacey mrlacey added the feature label May 11, 2017

@jamesmcroft

This comment has been minimized.

Show comment
Hide comment
@jamesmcroft

jamesmcroft May 13, 2017

Collaborator

Completely agree that this should be available.

With this, would we try to generate some basic UI tests for the pages that we add? Say for example, if we had a login page, would we write some UI tests for logging in etc.

Collaborator

jamesmcroft commented May 13, 2017

Completely agree that this should be available.

With this, would we try to generate some basic UI tests for the pages that we add? Say for example, if we had a login page, would we write some UI tests for logging in etc.

@jamesmcroft

This comment has been minimized.

Show comment
Hide comment
@jamesmcroft

jamesmcroft May 13, 2017

Collaborator

Thinking into this further though, would this be optional as it currently is when creating a new blank project?

Collaborator

jamesmcroft commented May 13, 2017

Thinking into this further though, would this be optional as it currently is when creating a new blank project?

@crutkas

This comment has been minimized.

Show comment
Hide comment
@crutkas

crutkas May 13, 2017

Member

Yes, I'm going to sync with Yosef Durr on the best way to integrate this support for WinAppDriver.

Member

crutkas commented May 13, 2017

Yes, I'm going to sync with Yosef Durr on the best way to integrate this support for WinAppDriver.

@crutkas crutkas added this to the Backlog milestone May 13, 2017

@mrlacey

This comment has been minimized.

Show comment
Hide comment
@mrlacey

mrlacey May 16, 2017

Collaborator

As a feature this becomes optional. In line with our current guidance, I was only thinking of a minimal test implementation with comments pointing to docs for more information.
@jamesmcroft in terms of more complex tests, perhaps they could be an "enhanced page feature"

Collaborator

mrlacey commented May 16, 2017

As a feature this becomes optional. In line with our current guidance, I was only thinking of a minimal test implementation with comments pointing to docs for more information.
@jamesmcroft in terms of more complex tests, perhaps they could be an "enhanced page feature"

@ralarcon

This comment has been minimized.

Show comment
Hide comment
@ralarcon

ralarcon May 19, 2017

Contributor

I agree with @mrlacey, we can explore the way to allow users to add a "UI test project" like other features... to implement testing logic would be really tough.

Contributor

ralarcon commented May 19, 2017

I agree with @mrlacey, we can explore the way to allow users to add a "UI test project" like other features... to implement testing logic would be really tough.

@mrlacey mrlacey modified the milestones: Backlog, 2.1 Mar 30, 2018

@mrlacey mrlacey self-assigned this Mar 30, 2018

@mrlacey mrlacey added the in-progress label Mar 30, 2018

mrlacey added a commit to mrlacey/WindowsTemplateStudio that referenced this issue Mar 30, 2018

Add WinAppDriver feature
For #300
currently C# only & doesn't work properly with VSEmulator

@mrlacey mrlacey modified the milestones: 2.1, 2.2 Apr 17, 2018

@mrlacey mrlacey modified the milestones: 2.2, 2.4, 2.3 May 23, 2018

@mrlacey

This comment has been minimized.

Show comment
Hide comment
@mrlacey

mrlacey May 23, 2018

Collaborator

Moving to the next milestone as this won't be ready by the localization deadline.

Collaborator

mrlacey commented May 23, 2018

Moving to the next milestone as this won't be ready by the localization deadline.

@mrlacey mrlacey modified the milestones: 2.3, 3.0 Jun 12, 2018

@mrlacey

This comment has been minimized.

Show comment
Hide comment
@mrlacey

mrlacey Jun 12, 2018

Collaborator

Moving to 3.0 as will be dependent upon solution level changes (for Any CPU)

Collaborator

mrlacey commented Jun 12, 2018

Moving to 3.0 as will be dependent upon solution level changes (for Any CPU)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment