Coded UI for Sharepoint Portals

Question

I am new for Coded UI. We want to use Coded UI to test Sharepoint portals.While running few tests, we came across the following questions.

How does it support if control Id's are generated dynamically?
How much support does it give to test Sharepoint out of box features?
Does it support Third-party asp.net controls?

Please let me know if you have any conclusion for these questions and also share the limitations of Coded UI for Sharepoint features.

Please provided useful links if any.

Micha · Accepted Answer · 2013-06-27 05:47:45Z

2

How does it support if control Id's are generated dynamically?

We have a (non Sharpoint) project with this situation. No problems until now. The record-tool finds normally enough informations (name, position, content, parent) to identify the control.

How much support does it give to test Sharepoint out of box features?

Sorry I haven't expirience to this, but can't imaging that there are to many problems.

Does it support Third-party asp.net controls?

Yes. We use controls form DevExpress - works fine.

Links

In this case I can really recommend you the MSDN Pages to this topic. They provide some good hints in context of working with CUIT.

answered Jun 27, 2013 at 5:47

Micha

5,1838 gold badges36 silver badges47 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

venkat Over a year ago

Thanks for you reply. Please give the searching criteria you used to identify control those Id's are generated dynamically in your project.

Micha Over a year ago

There is no universal answer to his. Mostly I take that what the record generates. Only sometimes I have to delete a generated criteria (very rarely).

Collectives™ on Stack Overflow

Coded UI for Sharepoint Portals

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related