Konstantin Vlasenko » Fitnesse

PowerShell: Wait for SQL Server is ready for client connections

Konstantin Vlasenko — Tue, 16 Aug 2011 15:36:53 +0000

The useful PowerShell script waiting SQL server is ready.
I found that waiting for starting service

while((get-service MSSQL`$INSTANCENAME).Status -ne 'Running'){Sleep 3}

is not enough.
Better to check the event log entry EventID = 17126: SQL Server is now ready for client connections. This is an informational message; no user action is required.

$ew = new-object system.management.ManagementEventWatcher
$ew.query = "Select * From __InstanceCreationEvent Where TargetInstance ISA 'Win32_NTLogEvent'"
while(!(get-eventlog -logname 'Application' -Source 'MSSQL$INSTANCENAME' | ? {$_.EventId -eq 17126})){
	$ew.WaitForNextEvent()
}

Removing Password Complexity Requirements from Windows Server 2008 Core

Konstantin Vlasenko — Wed, 27 Apr 2011 14:05:52 +0000

Use this PowerShell script if you need to remove Password Complexity Requirements from Windows Server 2008 Core:

secedit /export /cfg c:\new.cfg ${c:new.cfg}=${c:new.cfg} | % {$_.Replace('PasswordComplexity=1', 'PasswordComplexity=0')} secedit /configure /db $env:windir\security\new.sdb /cfg c:\new.cfg /areas SECURITYPOLICY del c:\new.cfg

PowerSlim v0.5 available

Konstantin Vlasenko — Thu, 24 Feb 2011 09:43:32 +0000

The new Remote feature available.
How it works:
1. Run PowerSlim server on the remote COMPUTER PowerShell -executionpolicy unrestricted -file .\slim.ps1 35 server
2. !define COMMAND_PATTERN (PowerShell -executionpolicy unrestricted -file .\slim.ps1)
3. |Query:Remote|Computer|Get-Service|
|DisplayName|Status|
4. Click TEST button.

How to start with PowerSlim

Konstantin Vlasenko — Mon, 31 Jan 2011 12:50:09 +0000

Install PowerShell (Windows 7 and Windows 2008 R2 already integrated with PowerShell)
Download latest fitnesse.jar file
java -jar fitnesse.jar. It’ll install itself
Unpack the latest PowerSlim into fitnesse folder. It will put the slim.ps1 file in it.
open localhost:80/PowerSlim
Click Suite button

Fitnesse 20110104 !include issue

Konstantin Vlasenko — Tue, 18 Jan 2011 08:00:08 +0000

The issue is not crucial but annoying.

!include -c CheckServices

Fitnesse tests in progress indication

Konstantin Vlasenko — Mon, 27 Dec 2010 12:57:20 +0000

For those using Fitnesse not only for fun but to test enterprise applications , we have made Fitnesse edition with the built-in indication of the tests currently in progress. Please check it out at https://github.com/downloads/konstantinvlasenko/fitnesse/fitnesse.jar
Hopefully Fitnesse will consider this improvement and merge it to the master branch.

Convert #JSON to #PowerShell

Konstantin Vlasenko — Wed, 27 Oct 2010 15:40:06 +0000

[Reflection.Assembly]::LoadWithPartialName("System.Web.Extensions")
$c = New-Object System.Web.Script.Serialization.JavaScriptSerializer
$c.DeserializeObject( $json )

#Selenium: UI-Element helps to insulate testcases from change in underlying application

Konstantin Vlasenko — Sun, 24 Oct 2010 20:10:43 +0000

With traditional Selenium IDE recorded tests, small modifications to the presentational layer of a web application can break the ability of the test to locate elements on a page. Tests should be more resilient to change, such that testcase breakage can be minimized with careful test construction, and can be fixed at a central point as opposed to in all affected testcases. This calls for some mechanism of abstracting the locator.

source: http://goo.gl/zJ8d

Selenium UI-Element Reference

Acceptance Test Rule #1

Konstantin Vlasenko — Wed, 08 Sep 2010 07:55:13 +0000

Implementation/Script of the Acceptance Test (AT) should not rely on a particular Virtualization Technology!

It is simple to understand that AT should be easy pointed to a different Virtual Machine. Also you should have an ability to switch between Virtualization Technologies (e.g. VMWare ESXi, MSFT Hyper-V) w/o changing AT’s implementation/Script.

PowerSlim: Run Fitnesse SLIM tests remotely

Konstantin Vlasenko — Wed, 01 Sep 2010 10:40:38 +0000

With PowerSlim you can run Fitnesse SLIM server remotely against your test environment (test VM).

You can do it using PowerShell 2.0 remoting.

In this case your PowerSlim server runs on the same machine as your Fitnesse server.

All you need is to enable PowerShell remoting on the test VM by executing the Enable-PSRemoting command.

Example:

!|script|PowerShell|

|eval|-Invoke-Command –computerName testVM { get-services }|

There are 2 benefits of this approach:

1. Clean test environment. You don’t need to run anything (except your production) on the test VM.

2. The ability to switch tests fast between VMs.