Is it possible to create our own object repository, so that it can be easily editable and maintained if any page element object get changed, as pages.g.cs file is read only?
Problem we are facing is that our Automation Test Suite would be having thousand of test cases and to maintain and update them as per any changes in application may become cumbersome for us without any updatable Object repository. Please suggest a work around for this.
Thanks,
Anuj
2 Answers, 1 is accepted
First, why is Pages.g.cs file read-only in your environment? Did you check it into your source control? If yes, please remove it from your source control ASAP. It does not belong under source control. The reason is that this file is automatically (and very frequently) automatically regenerated by Test Studio. There is no need for it to be under source control.
Second, I don't understand why you want to create your own element repository. Test Studio excels and maintaining the repository for you. Our Elements Explorer is a list of all of the elements used by all of your tests contained in your test project. You make changes via our Elements Explorer UI and those changes are instantly reflected in the Pages.g.cs file.
What advantage is there to creating your own that is separate from our Pages.g.cs file? Technically you can do anything you want in code. However you cannot create one that will replace Pages.g.cs such that non-coded steps will use it. The primary problem is that each test maintains its own elements that that test references. Non-coded steps don't even use Pages.g.cs.
Cody
the Telerik team
Test Studio Trainings
Rank 1
It helps using Elements Explorer