Make the New-Fixture function accepts "." (the current workding directory) as the $path parameter

In the past when we run the follow code, we will get errors.

PS C:\temp> New-Fixture . HelloWorld
Test-Path : Cannot bind argument to parameter 'Path' because it is an empty string.
At C:\Users\eyang\Documents\WindowsPowerShell\Modules\Pester\Pester.psm1:197 char:25
+     if (-not (Test-Path $path)) {
+                         ~~~~~
    + CategoryInfo          : InvalidData: (:) [Test-Path], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,Microsoft.PowerShell.Commands.TestPathCommand

Creating => \HelloWorld.ps1
Creating => \HelloWorld.Tests.ps1
PS C:\temp>

Now the $path parameter accepts ".". 

PS C:\temp> New-Fixture . HelloWorld
Creating => C:\temp\HelloWorld.ps1
Creating => C:\temp\HelloWorld.Tests.ps1
PS C:\temp>
throw an exception when test script block of `It` is not provided,
if user adopts ANSI (Allman) style to put open curly brace on a new line
add test for `It` if no test block is given
Merge pull request #90 from xinhuang/master

throw an exception when test script block of `It` is not provided,
Update CHANGELOG.md
Change colors of output to dimmer colors.

Changed the color of the output to make it readable on black, dark blue
and white background. Describe is now magenta instead of yellow and
passed tests are dark green.
Merge pull request #92 from nohwnd/master

Change colors of output to dimmer colors.
Merge pull request #86 from ogrishman/patch-2

Make the New-Fixture function accepts "." (the current workding director...
updates for latest merged in PRs
Fix a typo.
Merge pull request #96 from pullrich/master

Fix a typo.
TestDrive implemented

The test drive is created in describe and when moving to Context its
"state" is saved. When moving from the context files created in context
are deleted. This is done purely on full path basis so changes made in
context to Describe-scope files are kept. All test drive functions moved
to TestDrive. All tests regarding the test drive  moved to
TestDrive.ps1. Change to the Global scope polluting test were needed.
The test is not working properly anyway.  :(
this should fix the build. weird 3.0 and 2.0 differences
Random directory for TestDrive.

Test drive is set to random directory. The global $TestDrive variable
and global PSDrive TestDrive are still published but now the Pester
should not step on its own toes when executed in two separate processes
at the same time.

making tests work if env:temp ends with a slash

updating CHANGELOG
Merge branch 'random_testdrive_dirs'
make Get-TestTime culture agnostic

On cs-CZ, de-DE and other systems where decimal separator is different
than ".". Value [double]3.5 is output as 3,5 (or similar). Currently
this only makes some of the tests fail, but it could also leak to the
nUnit report if the time was output.
Add case sensitive assertions

Assertions are by default case insensitive and there is no intuitive way
to make the assertion case sensitive.
Adding new *Exactly assertions that use -c* operators to be case
sensitive.
Also naming fixes in the Contains and Match assertions.
make Get-TestTime culture agnostic

On systems with culture set to CZ, DE and other systems where decimal
separator is different than ".". Value [double]3.5 is output as 3,5 (or
similar). Currently this only makes some of the tests fail, but it
could also leak to the nUnit report if the time was output.
Merge pull request #111 from nohwnd/TestResultCultureAgnostic

make Get-TestTime culture agnostic
Add case sensitive assertions

Assertions are by default case insensitive and there is no intuitive way
to make the assertion case sensitive.
Adding new *Exactly assertions that use -c* operators to be case
sensitive.
Also naming fixes in the Contains and Match assertions.