function Merge-Hash{
param($parentHash, $childHash)

foreach ($childKey in $childHash.keys){
$parentHash.$childKey = $childHash.$childKey
}

return $parentHash
}

To test it, you can use this simple call in powershell

$hash1 = @{“a”=”1″;”b”=”2″;”c”=”3″}

I have several powershell scripts that I want to trigger via website, these scripts will start doing a lot of things on different computers on my network. We chose to use PowershellASP as the website server app, that allows you to call PS scripts from withing the HTML. This product works great! Check it out.

The Problem:

If you wish to invoke a command with PSASP, you just put in a PS snippet in HTML and your script is ran

<% Invoke-Command -ScriptBlock { Get-Services }

You will be redirected to a page, which will have the output from your command. This is all good and great, but what if you want to do multiple tasks on multiple computers at the same time? Then you need to start some background jobs. However, it seems that background jobs only run in the current PS window, and if you close the window down, the job is terminated. This becomes a problem because you do not have a continuous window in PSASP, and as soon as you start the background process the ASP process is terminated and your job with it.

The Solution:

What you need to do is start a process Start-Process cmdlt. Keep in mind that start-process starts executables. So, we have to execute the powershell.exe and pass in a .ps1 file as an argument. This file will do our job for us J

Here is some code:

<%

$ps = "C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe"

$working_dir = "C:\temp\ " #location of the ps.1 scripts to be executed

$script = ".\process.ps1"

$script2 = ".\process2.ps1"

cd $working_dir #Go into the working dir, for some reason

#-WorkingDirectory Switch did not work for me

Start-Process $ps $script -RedirectStandardError “C:\TEMP\error.txt” -RedirectStandardOutput “c:\TEMP\out.txt”

Start-Process $ps $script2 -RedirectStandardError “C:\TEMP\error2.txt” -RedirectStandardOutput “c:\TEMP\out2.txt”

%>

Please notice that I’m redirecting the standard error and standard out into a file, this is the only way you will be able to debug, otherwise the Start-Process will swallow any error you get before you have a chance to actually see it.

Finally, put something inside the 2 scripts you will run, and give this a try J

Invoke-Command -ScriptBlock {

Start-Sleep 15

“Job 1 Complete!” | Out-File “C:\temp\success.txt”

}

This script is super simple, sleep for 15 seconds then output something into file. Both of my scripts did this at different intervals so you can see them as they finish up.

You cannot go to a website without running into some form of Ajax. It’s great and all, but if you are trying to test a website with Selenium, this becomes an issue. Selenium will wait for the page to load, but is rather clueless when it comes to Ajax.

After spending several painful hours looking for a way to make a “wait_for_ajax” function, I found several solutions that do not work.

1 – Put sleep in your test.

Well obviously this is the simplest solution, but also the worst. We don’t know how long a request will take to load, what if the server is slow?

2- Use “waitForElement” command built into selenium

This is a better solution; we wait for a certain element, which is part of the Ajax response to appear before moving on. The problem with this solution is that we need to always know which element needs to load. This becomes a headache for us normal people with extra large web applications to support.

SOLUTION!

Here is the solution I stopped on. I won’t take credit for making it, but I’ll take some credit for compiling it all in one place. To be honest I have not seen it done yet, the only thing I’ve seen was for bits and pieces but not the whole problem.

To solve this problem, what we have to do is ask the browser to tell us how many active connections to the server are present. Then we sit and wait for that number to become 0. At this point we know that all Ajax requests went through and done, and we can move on in the test. (If you have a webapp that contains non-stop Ajax request to constantly update everything, you have my sympathy.)

Step 1: Figure out which Javascript library your application uses

This is important one, which had me stomped for a long time. Different libraries (Prototype, Dojo, jQuery) use different methods to retrieve the connection info.

Step2: Create the wait_for_ajax method

def wait_for_ajax(timeout=5000)

js_condition = “”

$selenium.wait_for_condition(js_condition, timeout)

end

Let’s break this one down.

• We have a default value of 5000 milliseconds for this method, but user can up or down it as they need.
• js_condition will be a string, which will contain a selenium call to the browser’s javascript. It will be a javascript conditional that will wait for active connections to be 0, and then return “true”
• $selenium.wait_for_condition is the method that will sit and wait for the javascript query to return “true” before letting you move on.

Step 3: Getting the right JS query for your library.

This part was the one, which took me the longest to figure out. But I’ll give you all the answers here. Different libraries use different functions to check incoming connection, so pick the right one for you.

jQuery: “jQuery.active”

Prototype: “Ajax.activeRequestCount”

Dojo: “dojo.io.XMLHTTPTransport.inFlight.length”

Step 4: Put together the JS search string

“selenium.browserbot.getCurrentWindow().” + library specific string + “ == 0”

Final string for jQuery will look like this

js_condition = “selenium.browserbot.getCurrentWindow().jQuery.active == 0”

Step 5: Put the method all together and enjoy

def wait_for_ajax(timeout=5000)

js_condition = “selenium.browserbot.getCurrentWindow().jQuery.active == 0”

$selenium.wait_for_condition(js_condition, timeout)

end

If I’m missing something, let me know. But spread the word, I know many of selenium users need this.