Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add test for update to Add-PoshGitToProfile #452

Merged
merged 3 commits into from
Mar 3, 2017

Conversation

rkeithhill
Copy link
Collaborator

@rkeithhill rkeithhill commented Mar 3, 2017

This test checks that the command creates the profile parent dir (or any in the path) if they don't exist. The command was modified to create any dir in the path by the addition of the -Force parameter on New-Item.

Follow-up on #449

rkeithhill and others added 2 commits March 2, 2017 21:08
This test checks that the command creates the profile parent dir (or any in the path) if they don't exist.  The command was modified to create any dir in the path by the addition of the -Force parameter on New-Item.
@dahlbyk dahlbyk force-pushed the rkeithhill/add-pester-test-for-create-profile-dir branch from a6eaa43 to 0a72234 Compare March 3, 2017 05:10
@dahlbyk
Copy link
Owner

dahlbyk commented Mar 3, 2017

Simplify missing profile parent test

For your consideration... since we already have cleanup infrastructure (for the record, Remove-Item -Recurse works fine on file paths), the test seems cleaner without the try...finally.

@rkeithhill
Copy link
Collaborator Author

rkeithhill commented Mar 3, 2017

Nice! I got hung up on $profilePath being a generated filename (not a dir) but yeah, deleting the file and usurping that name for the dirname does make this cleaner. Thanks!

@dahlbyk dahlbyk merged commit 88416ba into master Mar 3, 2017
@dahlbyk dahlbyk deleted the rkeithhill/add-pester-test-for-create-profile-dir branch March 3, 2017 06:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants