login vsi company logo login vsi company logo 250x40
header-05.jpg

normal Allow "App_Start" function without requiring window title

  • simonplant
  • simonplant's Avatar Topic Author
15 Jan 2015 14:14 #2302 by simonplant
simonplant created the topic: Allow "App_Start" function without requiring window title
We have both a dynamic application (window title changes) so I just want to launch it at the start of a test run and just let it close when the session logs out. Right now I can't do this without knowing the window title.

The request is the ability to start arbitary applications in a session without needing window title.

Please Log in to join the conversation.

More
15 Jan 2015 16:50 #2305 by o.bouhaj
o.bouhaj replied the topic: Allow "App_Start" function without requiring window title
We have several ways:

1= App_Start("", "", "", "", "")

Example: App_Start("WinWordOffice", "", "%VSI_Userhome%\UserEdit.doc", "Title", "UserEdit")

Explanation: Start App("<logname>", "", "<file-location>\<file-name>", "<search-for-title>", "<t-itle-name>")
Works when FTA is functional.

2= App_Start("", "", "", "", "", "", "")

Example: App_Start("Notepad", "c:\windows\system32", "notepad.exe", "Title", "Notepad", "Some text found in the document or app", "H:\document.txt")

Explanation: Start App("<logname>", "<folder-location>", "<file-executable-name>", "<search-for-title>", "<t-itle-name>, "<search-for-specific-text>", "<start-app-from-file-location>\<file-name>")

It is not required to use each Parameters.

For example in your case:
App_Start("WinWordOffice", "", "%VSI_Userhome%\UserEdit.doc", "Title", "")
or
App_Start("WinWordOffice", "", "%VSI_Userhome%\UserEdit.doc", "", "")
or
App_Start("Notepad", "c:\windows\system32", "notepad.exe", "Title", "", "", "H:\document.txt")
or
App_Start("Notepad", "c:\windows\system32", "notepad.exe", "", "", "", "H:\document.txt")
or
App_Start("Notepad", "c:\windows\system32", "notepad.exe", "", "", "", "")

You can, depending if you want to close it the normal way or not, keep it open until a user logs out when the user finishes it workload, or, use (depending on the version of the tool)
VSI_KillProcess("<logname>", "<appname>.exe").
Example: VSI_KillProcess("Notepad", "notepad.exe")

Because if there is 'no' window to focus on - there is unfortunately no other option to gracefully close it.

Please Log in to join the conversation.

  • simonplant
  • simonplant's Avatar Topic Author
16 Jan 2015 09:53 #2306 by simonplant
simonplant replied the topic: Allow "App_Start" function without requiring window title
Thanks Omar,
Then its a problem with the documentation on www.loginvsi.com/documentation/Workload_...ence_Guide#App_Start

The App Start call has this as the syntax:
App_Start("Logname ", " Working directory", " Executable or full path", " Window search mode", "Window title ", ["Window content "], ["Command line parameters"])

It is common practice to use [ ] to show optional parameters. Since [ ] are only used on the Window Content and Command line Params, it infers only those are optional and all other parameters are required, hence my request above.

If [ ] is not used to show optional parameters, perhaps you could explain what they are used for in the documentation please?

Thanks
Si

Please Log in to join the conversation.

What our customers are saying

Todd Mace - PernixData

"Login VSI has been a great partner for us. Customers use PernixData with Login VSI to help validate their user experience. Login VSI helps to see what their performance bottlenecks are and our software helps to mediate some of that. Login VSI has been a kind of defacto standard to be able to help that validation and help the customer to be able to come up with a solution to fix it."

Todd Mace, Product Manager at PernixData


Andrew Mills - Nutanix

“Predictability is a key piece to VDI. It’s one of reasons that VDI has scared people away, but Login VSI solves that. If you’re going to do it, do it right. Login VSI really gives that rubber stamp on doing it right.”

Andrew Mills, VDI Alliances Manager at Nutanix


Shaun Donaldson - Bitdefender

"As a software vendor, the reason that we became a Login VSI customer is that we wanted to see how we compared to our competitors. After talking to VMware and Citrix about how they test their products, it became clear to me that we needed to follow our strategic partners and be able to show how our product compares favorably to our competitors. We just completed a round of tests using Login VSI and you will see white papers showing performance data."

Shaun Donaldson, Alliances Director at Bitdefender

Login VSI, Inc.

300 Tradecenter

Suite 3460
Woburn, MA 01801

Phone: +1 844 828 3693

Login VSI B.V.

De Entree 85
1101 BH Amsterdam
The Netherlands

Phone: +31 20 705 1200