Skip to content

Import WindowsPhoneDriver as Winium.Silverlight#164

Merged
NickAb merged 29 commits into2gis:masterfrom
bayandin:the-merge
Oct 18, 2016
Merged

Import WindowsPhoneDriver as Winium.Silverlight#164
NickAb merged 29 commits into2gis:masterfrom
bayandin:the-merge

Conversation

@bayandin
Copy link
Copy Markdown
Contributor

@bayandin bayandin commented Oct 11, 2016

  • Migrate Tests
  • Service scripts (like PrepareRelease.ps1)
  • Documentation (at least README)

Copy link
Copy Markdown
Contributor

@NickAb NickAb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Skimmed over the changes. I'll try to take deeper look at this one as soon as on Friday.

#region Public Properties

public const string FileName = ".Winium.StoreApps.ConnectionInformation.json";
public const string FileName = ".Winium.Mobile.ConnectionInformation.json";
Copy link
Copy Markdown
Contributor

@NickAb NickAb Oct 12, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should look into backwards compatibility and support both names for a couple of releases. If new file is not found, then it should fallback to the old one and log warning message.

Copy link
Copy Markdown
Contributor Author

@bayandin bayandin Oct 12, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wouldn't say that this is backwards compatibility issue. Public API wasn't changed. Do we support work for different driver/server versions?
Will have a look at this case later.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will take a look at this myself. It would be nice to have a gradual transition if it easy to implement. Else we should include some useful message if not connection file was found, so it would be easy to pinpoint the problem of incompatible driver and inner server by end user, who might have messed with versions of inner and outer parts.

<Import Project="$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props" Condition="Exists('$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props')" />
<PropertyGroup>
<MinimumVisualStudioVersion>12.0</MinimumVisualStudioVersion>
<MinimumVisualStudioVersion>11.0</MinimumVisualStudioVersion>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why visual studio version has been downgraded? What version of VS did you use to make changes?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have no idea why VS has decided to downgrade it. It happened when I added target for WP Silverlight 8.1
I use VS Enterprise 2015 (14.0.25431.01 Update 3).

<TargetFrameworkProfile>Profile151</TargetFrameworkProfile>
<TargetFrameworkVersion>v4.6</TargetFrameworkVersion>
<TargetFrameworkProfile>Profile259</TargetFrameworkProfile>
<TargetFrameworkVersion>v4.5</TargetFrameworkVersion>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it because of Silverlight support?

Copy link
Copy Markdown
Contributor Author

@bayandin bayandin Oct 12, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think so. I'm not an expert in build target in VS I see this and can't change any version:

screenshot 2016-10-12 11 04 29

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please try to add target for Silverlight by yourself (you need to replace 89035d8 commit)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will check this.

this.PingTimeout = DefaultPingTimeout;
this.NoFallback = true;
this.CommandSettings = new CommandSettings();
this.IsJavascriptEnabled = true;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it required to call ExecuteScript in some selenium bindings? In python selenium bindings do not check this flag at all and allow calling ExecuteScript commands anyway.

It is minor, but will be nice to check this, because it implies javascript support, not some custom "scripting" support.

Copy link
Copy Markdown
Contributor Author

@bayandin bayandin Oct 12, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

EndGlobalSection
GlobalSection(SolutionConfigurationPlatforms) = preSolution
Debug|Any CPU = Debug|Any CPU
Debug|ARM = Debug|ARM
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need that much configurations. Visual Studio creates them automatically when any project is added. Need to investigate if that can be prevented in future. Meanwhile, simple deletion of unnecessary configurations will suffice.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't mind to remove it, but why do we care about it?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When building Debug or Release configuration it will build for all platforms (x86, arm, anycpu), which is redundant in our case. You will also have to maintain these configuration when adding new projects, etc, because sometime VS does not add new projects to each configuration correctly.

@bayandin
Copy link
Copy Markdown
Contributor Author

@NickAb ok, it seems it's ready 🎆

@bayandin bayandin changed the title [WIP] Import WindowsPhoneDriver Import WindowsPhoneDriver as Winium.Silverlight Oct 17, 2016
@NickAb NickAb merged commit 2f18645 into 2gis:master Oct 18, 2016
@NickAb
Copy link
Copy Markdown
Contributor

NickAb commented Oct 18, 2016

@bayandin Thanks, merged 👍

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants