This is a migrated thread and some comments may be shown as answers.

Keep WPF application open for the next test

7 Answers 262 Views

General Discussions

This is a migrated thread and some comments may be shown as answers.

7 Answers, 1 is accepted

Elena

commented on 17 Jul 2024, 01:46 PM

My issue is related to the above so can I please have some guidance with the below?
I have the following scenario: I record a test for Login functionality, a second test that uses the login + additional steps and a 3rd one that uses second test as test step + other steps.
If I put all these 3 tests in a list and run it it will result in doing the login and other common steps 2 or 3 times. What I want is to have the 3 test still separated in the project for easy maintenance, but when running these from the list to only execute the common steps once. Is this possible?

Elena

commented on 22 Jul 2024, 12:10 PM

Hi Elena,

The matter seems to be related to test organization. From what you describe the 3rd test is a complete scenario which reuses some common actions. What is the reason to include tests 1 and 2 and not use only test 3 as part of the test list?

Otherwise any test included in the test list will be executed during the run. If you don't need it, you can exclude it from the list.

I hope this helps.

Regards,
Elena Tsvetkova

answered on 24 Sep 2012, 03:22 PM

Hello Nathan,

The problem here is that Test Studio internally calls the LaunchNewApplication() and ActiveApplication.Quit() methods automatically. If you really want to start the application with code instead of using the Configure window, you can use one of the following methods.

Create a Unit test or convert your existing test to a Unit test using the "Convert All Steps To Code" feature. The disadvantages of this are that a unit test cannot be converted back to a Test Studio test and you have to do all the work using code.
Create a mock application to feed to Test Studio. Then insert a coded step as the first step of the test. Use the following code which closes the mock application and launches the desired application.

//Close the mock application

ActiveApplication.Quit();

//Launch an application of your choice

Manager.LaunchNewApplication(@"C:\Release\PhotoDemo.exe");

//Refresh Visual Tree

Manager.ActiveApplication.MainWindow.RefreshVisualTrees();

To stop the application from closing:

Select the last step from a Test Studio test and set the Pause Test Step Property to After. This will pause the test after that step leaving the app opened.
If you are using a Unit test, simply don't use the ActiveApplication.Close() method at the end of the test.

Just out of curiosity, why do you need this? How does it help your test automation?

All the best,

Plamen
the Telerik team

Are you enjoying Test Studio? We’d appreciate your vote in the ATI automation awards.
Vote now

answered on 29 Aug 2014, 09:16 AM

Hi Plamen,

I have a question related to active application open and close. The scenario is that I am creating two coded steps in a single WPF test file.
In first coded step, I opened the application through manager.activeapplication , then a scenario in it and then close the app through  wpfApp.MainWindow.Window.Close();
Now in my next coded step , I again want to open this application for some different scenario but neither manager.activeapplication nor manager.launchnewapplication is working.

Please suggest how to achieve that. Below is the code:

public class WpfTest1 : BaseWebAiiTest
{
#region [ Dynamic Applications Reference ]

private Applications _applications;

/// <summary>
/// Gets the Applications object that has references
/// to all the elements, windows or regions
/// in this project.
/// </summary>
public Applications Applications
{
get
{
if (_applications == null)
{
_applications = new Applications(Manager.Current);
}
return _applications;
}
}

#endregion

[CodedStep(@"Open a Station in a casino for a new game day")]
public void WpfTest1_CodedStep()
{

WpfApplication wpfApp = Manager.ActiveApplication;
Assert.IsTrue(wpfApp.GetWindow("Warnung") != null);

Button Ok = (wpfApp.GetWindow("Warnung").Find.ByName<Button>("OK"));

Ok.User.Click();
Thread.Sleep(1000);

Assert.IsTrue(wpfApp.MainWindow.Window.Caption != null);

var row = wpfApp.MainWindow.Find.ByName<DataGrid>("Stations");
var rows = row.RowElements;

var availableRow = rows.FirstOrDefault(stationRow => stationRow.TextBlockContent.Contains("Offnen"));

if (rows.Count > 0 && availableRow != null)
{
availableRow.User.Click();
Thread.Sleep(1000);

wpfApp.MainWindow.Find.ByName<Button>("OpenStation").User.Click();
}
else
{
wpfApp.MainWindow.Window.Close();



}

}


[CodedStep(@"Open an already opened station(samehostname) in a Casino")]
public void WpfTest1_CodedStep1()
{
WpfApplication wpfApp = Manager.LaunchNewApplication(@"E:\Builds\Build_27August2014\Bin");
Assert.IsTrue(wpfApp.GetWindow("Warnung") != null);

Button Ok = (wpfApp.GetWindow("Warnung").Find.ByName<Button>("OK"));

Ok.User.Click();
Thread.Sleep(1000);

Assert.IsTrue(wpfApp.MainWindow.Window.Caption != null);

var row = wpfApp.MainWindow.Find.ByName<DataGrid>("Stations");
var rows = row.RowElements;

var availableRow = rows.FirstOrDefault(stationRow => stationRow.TextBlockContent.Contains(Environment.MachineName));
if (rows.Count > 0 && availableRow != null)
{
availableRow.User.Click();
Thread.Sleep(1000);

wpfApp.MainWindow.Find.ByName<Button>("OpenStation").User.Click();
}
else
{
wpfApp.MainWindow.Window.Close();
}
}

}

}

Elena

commented on 22 Jul 2024, 11:56 AM

Hi Chad,

I wanted to step in and add up to my colleague's response - although the feature is not available out of the box, there are a couple of workarounds which you may find useful. Please, find these in this article.

Best,
Elena