Getting local tests to fail #7535
Replies: 5 comments
-
I ran this on a Windows 2008 R2 machine with PSv3 and could not get it to break. Arg. |
Beta Was this translation helpful? Give feedback.
-
Testing locally on appveyor works 😡 So far, I'm leaning this works, it's just appveyor, suddenly |
Beta Was this translation helpful? Give feedback.
-
K, I've determined that appveyor just chose these commands to to fail. I'll add them to pester_groups to skip and uncomment a lot of others that failed with previous versions of SMO |
Beta Was this translation helpful? Give feedback.
-
Removed these from the ignore group, so we'll have to keep an eye if they work better with the new SMO
|
Beta Was this translation helpful? Give feedback.
-
Resolved ✔️ |
Beta Was this translation helpful? Give feedback.
-
I'm working on a whole upgrade of SMO which requires an upgrade of our library.
There are like 4 tests that fail on appveyor that I can't get to fail locally. Can you? The branch is
smonewest
.Note that you will have to close out every open copy of PowerShell and VSCode to switch branches as there are a bunch of DLLs being swapped out.
The commands I can't get to fail locally are:
Get-DbaUserPermission
- Can you get it to return nothing forGet-DbaUserPermission -SqlInstance $script:instance1 -Database tempdb
Install-DbaDarlingData
- Install itSync-DbaLoginPermission
- Can you sync some perms?Invoke-DbaBalanceDataFiles
- Can you get it to not work?I manually copied the commands ran in each of the .Tests.ps1 and cannot get these to fail but I don't want to just ignore them just yet because they may be a canary.
Beta Was this translation helpful? Give feedback.
All reactions