Downloads:

4,641

Downloads of v 2.3.0:

406

Last Update:

29 Apr 2016

Package Maintainer(s):

Software Author(s):

  • Akira Sugiura

Tags:

tdd isolation mock mocks mocking fake fakes faking unittest unittesting

Prig - Open Source Alternative to Microsoft Fakes

This is not the latest version of Prig - Open Source Alternative to Microsoft Fakes available.

2.3.0 | Updated: 29 Apr 2016

Downloads:

4,641

Downloads of v 2.3.0:

406

Maintainer(s):

Software Author(s):

  • Akira Sugiura

Prig - Open Source Alternative to Microsoft Fakes 2.3.0

This is not the latest version of Prig - Open Source Alternative to Microsoft Fakes available.

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test


Validation Testing Passed


Verification Testing Exempt:

Requires Visual Studio

To install Prig - Open Source Alternative to Microsoft Fakes, run the following command from the command line or from PowerShell:

>

To upgrade Prig - Open Source Alternative to Microsoft Fakes, run the following command from the command line or from PowerShell:

>

To uninstall Prig - Open Source Alternative to Microsoft Fakes, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade prig -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade prig -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure prig installed
  win_chocolatey:
    name: prig
    state: present
    version: 2.3.0
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'prig' do
  action    :install
  version  '2.3.0'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: prig,
    Version: 2.3.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller prig
{
   Name     = 'prig'
   Ensure   = 'Present'
   Version  = '2.3.0'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'prig':
  provider => 'chocolatey',
  ensure   => '2.3.0',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install prig version="2.3.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 29 Apr 2016.

Description

Prig(PRototyping jIG) is a framework that generates a Test Double like Microsoft Fakes/Typemock Isolator/Telerik JustMock based on Unmanaged Profiler APIs. This framework enables that any methods are replaced with mocks. For example, a static property, a private method, a non-virtual member and so on.


tools\ChocolateyInstall.ps1
# 
# File: ChocolateyInstall.ps1
# 
# Author: Akira Sugiura ([email protected])
# 
# 
# Copyright (c) 2015 Akira Sugiura
#  
#  This software is MIT License.
#  
#  Permission is hereby granted, free of charge, to any person obtaining a copy
#  of this software and associated documentation files (the "Software"), to deal
#  in the Software without restriction, including without limitation the rights
#  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
#  copies of the Software, and to permit persons to whom the Software is
#  furnished to do so, subject to the following conditions:
#  
#  The above copyright notice and this permission notice shall be included in
#  all copies or substantial portions of the Software.
#  
#  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
#  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
#  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
#  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
#  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
#  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
#  THE SOFTWARE.
#


'  Installing Prig.vsix...'
$packageName = 'Prig'
$vsixUrl = 'https://github.com/urasandesu/Prig/releases/download/v2.3.0/Prig.vsix'

Install-ChocolateyVsixPackage $packageName $vsixUrl
tools\ChocolateyUninstall.ps1
# 
# File: ChocolateyUninstall.ps1
# 
# Author: Akira Sugiura ([email protected])
# 
# 
# Copyright (c) 2015 Akira Sugiura
#  
#  This software is MIT License.
#  
#  Permission is hereby granted, free of charge, to any person obtaining a copy
#  of this software and associated documentation files (the "Software"), to deal
#  in the Software without restriction, including without limitation the rights
#  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
#  copies of the Software, and to permit persons to whom the Software is
#  furnished to do so, subject to the following conditions:
#  
#  The above copyright notice and this permission notice shall be included in
#  all copies or substantial portions of the Software.
#  
#  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
#  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
#  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
#  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
#  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
#  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
#  THE SOFTWARE.
#


'  Uninstalling Prig.vsix...'
$vscomntoolsPaths = gci env:vs* | ? { $_.name -match 'VS\d{3}COMNTOOLS' } | sort name -Descending | % { $_.value }
if (0 -eq $vscomntoolsPaths.Length) {
    Write-Error "'VsDevCmd.bat' is not found."
    exit 1805378044
}
$vsDevCmdPath = [System.IO.Path]::Combine($vscomntoolsPaths[0], 'VsDevCmd.bat')
if (![System.IO.File]::Exists($vsDevCmdPath)) {
    Write-Error "'VsDevCmd.bat' is not found."
    exit 1805378044
}
cmd /c ('" "{0}" & vsixinstaller /q /u:0a06101d-8de3-40c4-b083-c5c16ca227ae "' -f $vsDevCmdPath)

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Prig - Open Source Alternative to Microsoft Fakes 2.3.1 647 Sunday, August 14, 2016 Approved
Prig - Open Source Alternative to Microsoft Fakes 2.3.0 406 Friday, April 29, 2016 Approved
Prig - Open Source Alternative to Microsoft Fakes 2.2.0 300 Sunday, February 21, 2016 Approved
Prig - Open Source Alternative to Microsoft Fakes 2.1.1 266 Saturday, January 23, 2016 Approved
Prig - Open Source Alternative to Microsoft Fakes 2.1.0 276 Sunday, December 20, 2015 Approved
Prig: Open Source Alternative to Microsoft Fakes 2.0.0-alpha06 290 Friday, September 18, 2015 Exempted
Prig: Open Source Alternative to Microsoft Fakes 2.0.0-alpha05 273 Saturday, August 1, 2015 Exempted
Prig: Open Source Alternative to Microsoft Fakes 2.0.0-alpha04 319 Wednesday, May 27, 2015 Exempted

Version 2.3.0

  • Fixed the issue that stack trace isn't outputted in Windows 10. It seems that this correction doesn't effect against Windows 7 and Windows 8.1. There is a high probability that we used wrongly the api that handles stack trace.
  • Update middleware. NUnit is updated from 2.6.3.13283 to 2.6.4.14350.
  • Fixed #60: Don't create log directory in various places. When installing, add the environment variable to indicate the log directory. Also, remove the variable when uninstalling.
  • Fixed #62: Propose empty mock implementation for replacement target method. Improve Get-IndirectionStubSetting command more explanatorily. By the way, I added some code snippets, but it is an experiment -- possibly, they are removed at next release.
  • Fixed #64: Any Prig Assembly addition is failed in the environment that the environment variable VS###COMNTOOLS is installed only one. Fix the script bug.
  • Fixed #65: Prig cannot handle type reference generic parameter constraint. Change the AssemblyBuilderAccess of temporary assembly ReflectionOnly to Run, because it conflicts with the assembly that has been already loaded as runnable(this behavior is uncontrollable).
  • Fixed #66: Register Prig menu doesn't work in a x86 environment. Fix the behavior to choose the file path depends on the processor architecture.
  • Fixed a regression caused by Visual Studio 2015 support.
  • Fixed some potential bugs.

Version 2.2.0

  • Fixed #57: Support for Continuous Integration Server (like AppVeyor). Add some special APIs and maintenance document to explain them. For details, please see our Wiki.
  • Fixed #58: Needs more robustness for additional delegates. Ignore the additional delegate that doesn't exist, because build error occurs even if the delegate doesn't relevant.
  • Fixed potential bugs. Some multiple threads race conditions existed. These were found by Coverity.

Version 2.1.1

  • Update middleware. Boost is updated from 1.55.0 to 1.60.0.
  • Fixed infrastructure's bug. The function to parse PE header was wrong. This bug affected the environment installed Visual Studio 2015 or more. See also the comment of the issue.
  • Reduce environmental dependence. Until this improvement, Add-PrigAssembly command used absolute path instead of relative path or environment variable. So, any build will fail on another environment different from first setup without *.csproj modification.
  • Improve prig.exe help. Also, we maintain out wiki to explain it.

Version 2.1.0

  • Fixed #48: No longer need install.ps1 for NuGet. Clean up the content.
  • Fixed #49: Minimize the dependency to Chocolatey. Prig can support standalone installation via VSIX since this version.
  • Fixed #52: Support Visual Studio 2015 Update 1. Deal that the test execution engine is changed from vstest.executionengine to TE.ProcessHost.Managed.
  • Fixed some potentially bugs for prig command. It could not remove the symbolic link that has been already moved. Additionaly, improve some error messages.

Version 2.0.0

  • Fixed #31: Issue with out parameters.
  • Fixed #46: Support mocking DLL imports.
  • Against the comment-based help of Prig management commands, unified the definition of word because they were defined. See also our wiki.

Version 2.0.0-alpha06

  • Fixed #45: Support Visual Studio 2015
  • Fixed #44: Namespace reference not added for parameter that is array type
    [NOTICE] This issue has already been fixed in the family of V2. We just applied the fix to the family of V1.
  • Improve installation robustness. The ExecutionPolicy of PowerShell that is invoked during build tasks was sometimes unexpected, so modify to set explicit value.
  • Enhance supported signature. The unusual types that appear on the interface of a method is almost supported. For example, T[,][](T is a generic type parameter), List<DateTime[]>[,], out M[][,](M is a generic method parameter) and so on.
  • Prepare to support three or more out/ref parameters. By decreasing the dependencies of an indirection stub that profiler used, performance is also improved.

Version 1.1.1

  • [NOTICE] The family of v1 will be obsolete soon. We strongly recommend migrating to the family of the v2. About the way of the migration, please see our Wiki.
  • Support Visual Studio 2015.
  • Merge the fixes that were applied to the family of the v2.

Version 2.0.0-alpha05

  • Improve stability for the methods of the classes that are used on the boundary of application domains(e.g. AppDomain, BinaryReader, MemoryStream, Thread and so on).
  • Improve usability for the command to manage Prig a little(See also the Wiki).
  • Merge Infrastructure Bug Fix(See also Swathe issues #2)
  • Make the sequence that builds the indirection stub dll more efficient.

Version 2.0.0-alpha04

  • Update NUnit Test Adapter for Prig from based on 1.2.0 to based on 2.0.0.
  • [BREAKING CHANGE] To fix the following issues, alpha04 has lost compatibility with alpha03. Also, choco upgrade command cannot even work. I will publish the migration steps in this page as soon as possible.
  • Fixed #41: Error in remove prig assembly
  • Fixed #40: Test engine crashes while trying to execute a unit test without indirections context even when it doesn't use any stubs
  • Fixed #37: Suggestion add prig files as Copy If Newer to output directory
  • Fixed #33: Make framework assemblies private.
  • Implemented Experimentally #31: Issue with out parameters
  • Merge Infrastructure Enhancement(See also Swathe issues #1)
  • Fixed #36: If an assembly is added-removed multiple times there is duplicated prebuild steps
  • Fixed #35: Rebuilding after .prig file had types removed still contains removed types in prig assembly
  • Fix error when enabling Test Adapter and no vstest running
  • Fix more generation issues
  • Response to Strange Behavior. Depending on the replacing method, the static method of the infrastructure is sometimes called before initializing the field of the type. For example, you will find the behavior if you try a sample of Generics with Prig v2.0.0-alpha03 in Visual Studio integrated environment. It seems very strange behavior, but we have to consider that in this layer.

About more previous versions, please see https://github.com/urasandesu/Prig/releases.


This package has no dependencies.

Discussion for the Prig - Open Source Alternative to Microsoft Fakes Package

Ground Rules:

  • This discussion is only about Prig - Open Source Alternative to Microsoft Fakes and the Prig - Open Source Alternative to Microsoft Fakes package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Prig - Open Source Alternative to Microsoft Fakes, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus