I wish this knowledge was documented somehwere else besides a forum
We are constantly working on improving our documentation. Thank you for the feedback. I'll get this on our technical writers TODO list.
At this point, I would no longer return to either TTS or the Plugin. I'd keep working in "hand roll your own code mode". No more recording. Perhaps that was my mistake.
If you prefer to always convert your tests to NUnit coded unit tests that's fine too. It's just important to maintain the code that uses our Pages class, or remove it all together. When we generate code, we'll generate something like this:
Actions.SetText(Pages.AutomatedTestingGoogle.GbqfqText, "automated testing");
What's really important to note here is that "Pages.AutomatedTestingGoogle.GbqfqText" references a specific element on the current page AND it's using our Pages class from the generated Pages.g.cs file.
Even if you don't reference any elements using our Pages class our generated code includes this which also refers to our Pages class:
If you desire to break your dependency on our Pages class you need to remove/change any element references and remove the above section of code from the code our plug-in generates.
Also, I used to think that one could use the Plugin without having TTS? Is that not true?
Telerik Test Studio comes in three flavors:
Full edition - This includes our standalone IDE and the VS Plug-in
Test Studio Express - This flavor has been discontinued. It was the VS Plug-in only.
Run-Time edition - A trimmed down version of Test Studio. Includes only our services and command line tools. Intended to be used to create Telerik scheduling server, execution server, load controller, load agent, or installed on build servers.
Bottom line if you have installed our plug-in, by definition you have installed Telerik Test Studio.
Or is possible to "record" a selecting a collection of UI elements...
For those that want to you can use Add to Project Elements from our Elements Menu
. It's somewhat tedious because you have to add each element of interest one element at a time. The advantage is that the element you have selected is added to our Elements Repository
, which is then used to generate our Pages class which you can then use in your code.
...Correctly generated? Was it included in your Project or did you have to Right-click on it within VS Solution Explorer and include it into the Project?
Yes, yes and no (it was not explicity included in my VS project). Because I used the already customized .csproj file, Visual Studio knew to include it during the compile phase of the build. I would expect to have problems if I manually created an ordinary VS test project that didn't include our customization (the Import line I previously explained).
My initial gripe was, "why does it keep saying Pages.g.cs has been modified outside of the editor..." when I know that is CLEARLY not the case. And the video solution to "just close the Pages.g.cs file" was laughable. I'm sorry but it was.
On that point I do agree with you. We are needlessly regenerating this file too often i.e. we're too aggressive on when/how often it needs to be regenerated. We have this open bug report
on this behavior and it is actively being worked on by our development team.
All the best,
the Telerik team