SVN problems due to way WebUI automatically names pages

[Matt]

Hi,

We have a team of 4 users working on an automation project, and are using SVN to keep the project files updated etc

We are getting conflicts everytime team members try to commit to SVN, mainly in the Project.cs and .csproj files. We have tried manually merging to resolve the conflicts but our issues seem to arise due to the way WebUI automatically names pages in the project.cs file. So we are ending up with multiple instances of pages with the same names after merging. We could manually change the page names but this then would require also changing the relevant page names in all .aii tests which use the page. This is not feasible when we will have hundreds of test cases and pages further down the line.

Is there anyway we can stop WebUI automatically naming the pages the way it does and manually name them during test creation?

cheers

[Konstantin Petkov]

Hi Matt,

Thank you for contacting us and the question.

We actually reworked the page element generation algorithm due to these exact source controls conflicts related to merging the page element file. There is no Project.cs file anymore that need to be included in the project.

It seems you're running an older version of the product though. The latest official release from August (labeled 2010.2.830) includes the reworked algorithm and we highly recommend upgrading to that version. This should solve those source-control issues.

All the best,
Konstantin Petkov
the Telerik team

[Matt]

Hi,

Thanks for the quick reply.

The trial version for the last member in our team is due to run out in the next day, and before we decide to make a decision whether to purchase we would need to know that this functionality definitely solves our problem.

Is there any way we could get a new trial period to test this latest version out? 

[Konstantin Petkov]

Hello Matt,

Yes, we can extend his trial so that he can try the new version as well. Please ask him to submit that request via this form referring there your account email. Thank you!

Sincerely yours,
Konstantin Petkov
the Telerik team

[Matt]

Hi,

I have installed the latest version and can see that it does indeed no longer produce a Project.cs file.

However, before I get the rest of the team onto the new version I can see that WebUI still automatically names pages the same way it did before (just not storing them in a Project.cs file). When converting steps to code, we find that WebUI automatically names a page e.g. Pages.MyPage_1., Pages.MyPage_2

This is causing conflicts when numerous people are working on the project at once and submit their copies to SVN, as we are still having pages with the same name being created. Where are the references to these pages now kept if not in Project.cs, and are we still likely to get conflicts with numerous people working on the same project together as before, because as far as I can tell we are going to end up with multiple team members having pages with the same names still, is there a way we can specify the page naming convention without having to manually go through the code renaming everywhere where the page is referenced?

Cheers

[Konstantin Petkov]

Hello Matt,

No, you should no longer get those conflicts, this is why we reworked the page elements generation. Now we generate those elements on each build instead of keeping and referring them. We have not changed the naming algorithm but that should cause any conflicts (the root of the conflict wasn't the way we name the page elements).

Please also note WebUI Test Studio allows you to rename any element (page, an element within the page). Just select a step in the Steps and look for the page element in the Elements Explorer. When you load the Properties of that element look for a FriendlyName property. You can change that to change the element name we automatically generated.

Kind regards,
Konstantin Petkov
the Telerik team