An engineer is someone who can make for a dollar what any fool could make for two. – Alan Kay
Cmdlet Description Add-ADComputerServiceAccount Adds one or more service accounts to an Active Directory computer. Add-ADDomainControllerPasswordReplicationPolicy Adds users, computers, and groups to the Allowed List or the Denied List of the read-only domain controller (RODC) Password Replication Policy (PRP). Add-ADFineGrainedPasswordPolicySubject Applies a fine-grained password policy to one more users and groups. Add-ADGroupMember Adds one or more members [...]
Good news:) With Fitnesse + PowerSlim the problem described here can be solved gracefully. You can use Test-Path PowerShell CMDlet: !|script|PowerShell| |check|eval|Test-Path “C:\ExportEmpty\*”|False| |check|eval|Test-Path “c:\ExportNotEmpty\*”|True|
With powerslim you can Query a file. !|script|PowerShell| |eval |!-function get_lines($file){Get-Content $file | % {New-Object PSObject -Property @{Line=$_}}}-!| !|Query:PowerShell|get_lines c:\myfile.txt| |Line| |text at first line| |text at second line|
Check this interesting post from Mike. You will find an idea how to specify credentials w/o promt for PowerShell remote command execution. This is the common thing for the “Power Fitnesse” http://maplpro.blogspot.com/2010/03/powershell-20-plus-fitnesse-slim-plus.html
http://gojko.net/2009/09/24/top-10-reasons-why-teams-fail-with-acceptance-testing/ … – Tests unusable as live documentation – Focusing on tools – Not considering acceptance testing as value added activity – “Test code” not maintained with love – No management buy-in – Underestimating the skill required to do this well …
