Trouble getting instance of Object Repository from BrowserWindowUnderTest about cuite

[FantasticFiasco]

I am currently on vacation but can take a look at this in three days. Is that OK?

[Kritner]

No problem - just trying to get a better feel for the new syntax.

[FantasticFiasco]

I am party responsible for the new syntax :-)

The wiki is not up to date with the current syntax, but I think reading the unit tests are a good way to get to know it.

[icnocop]

BrowserWindowUnderTest.GetBrowserWindow<T>(); expects a constructor on type T which takes a string parameter for the title of the window.

You can either add a string parameter to the constructor or try to combine the Launch and GetBrowserWindow functions into one call as follows:

        LogInPage pgLogin = BrowserWindowUnderTest.Launch<LogInPage>(URL);

Thank you.

[Kritner]

@icnocop Thanks, I guess I could do that, but wouldn't I then run into the same issue for my second NewPage newPage = BrowserWindowUnderTest.GetBrowserWindow<NewPage>(); ? I was under the impression that BrowserWindowUnderTest.Launch would open a new URL, and my above was actually just an example, I'm actually doing a test with around 10 separate page flows, would I need to do a Launch for each of them, and know the URL to each of them in turn?

[FantasticFiasco]

@Kritner I would propose taking a look at the CUITe.ObjectRepository namespace. It contains a few nifty classes that enables you to make use of the Object Repository pattern when it comes to how you write your UI tests. There is a migration story there, one that you will have to put effort into doing, but I think it will pay off in the end. More information can be read in the closed pull request #44.

Once you've migrated to using the classes in namespace CUITe.ObjectRepository, you can then decide if you wan't to take it to a different level by implementing the feature called Workflows in CUITe, a feature that lets you combined a number of actions, like for instance the interaction between your 10 separate pages, into a workflow that can be reused between tests. For more information about workflows please read the information of the closed pull request #46.

[FantasticFiasco]

@Kritner Is it OK if we close this issue?

[Kritner]

Yeah - thanks