Notices: This section not yet converted to new layout. Download stats are rolling back out.

This is a prerelease version of LegiTest.



This package skips automatic verification:

Requires Visual Studio

This package was approved as a trusted package on 6/13/2017.


LegiTest is a comprehensive tool that allows you to test all your data-centric applications, in an easy-to-use, automated platform. It easily integrates with Visual Studio and your existing development software. LegiTest includes a 14-day free trial or enter your license key to access this full featured data testing suite.

LegiTest provides users a way to legitimize the data they provide to the decision makers within their organization.

LegiTest enables your team to test all aspects of the SQL Server stack. This includes testing of database objects such as stored procedures, functions, views and tables. It further includes all objects on the BI stack, including SSIS Packages, SSAS Cubes and Dimensions (both Tabular and Multidimensional) and SSRS reports.

LegiTest Highlights

  • Easy-to-use interface with no code writing necessary

  • Ability to manage your own data and test how you want

  • Simply integrates with build processes and development software you're already using

LegiTest Features

Comprehensive Test Coverage

Accurate data is necessary to any successful business. LegiTest offers users comprehensive test coverage for data-centric applications. It covers all aspects of the SQL Server stack, including SSAS, SSIS & SSRS, as well as any database with OLE DB, ODBC, or ADO.Net interfaces. LegiTest interacts with your data centric applications and will verify the results of your code and data.

Production Data Comparison

BI projects frequently interact with data stored in multiple locations and formats. LegiTest allows you to compare data across different platforms.

Test The Way You Want

Some testing tools expect you to adhere to a rigid format. LegiTest allows you to easily setup the necessary elements for your test, and to clean up afterwards. In addition, it support multiple execution tracks for tests, and lets you control the steps in the testing process.


With LegiTest, users are provided a responsive user interface that integrates into Visual Studio. Tests can be created using an easy graphical interface. There is no need to write code and complicated operations are wrapped up into easy to use actions and assertions.


While it is not required to write code in LegiTest, some users may want to add their own custom logic to the tests. LegiTest supports the addition of custom actions, assertions, and you can extend your test code directly.

Integrates with Existing Systems

Worried about how LegiTest will work with the systems you already have in place? It easily integrates with the products and processes you are currently using. It will generate tests that use common testing frameworks (MSTest, NUnit), and integrates well with build processes using TFS, Team City or MSBuild.

Problems Solved by LegiTest

How do you test your data-centric development today?

Most users are currently not testing their data thoroughly, using multiple products or are doing so manually. LegiTest provides users the ability to accurately test their data in one automated platform.

How long does it take to do comprehensive testing today?

It usually takes users an exorbitant amount of time to test their data since they have to compare it across multiple platforms or do it manually. LegiTest provides users with automated testing that can verify data-centric applications simply and quickly.

How are you validating the data loaded into your target systems?

LegiTest provides a single, comprehensive tool to ensure all aspects of your data-centric development are valid and legitimate.

To install LegiTest, run the following command from the command line or from PowerShell:

C:\> choco install legitest --version 2017.3.2.612-beta --pre

To upgrade LegiTest, run the following command from the command line or from PowerShell:

C:\> choco upgrade legitest --version 2017.3.2.612-beta --pre


  • tools\chocolateyinstall.ps1 Show
    $ErrorActionPreference = 'Stop';
    $packageName= 'legitest'
    $toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
    $url        = ''
    $packageArgs = @{
      packageName   = $packageName
      unzipLocation = $toolsDir
      fileType      = "MSU"
      url           = $url
      silentArgs    = "/qn /norestart /l*v `"$env:TEMP\chocolatey\$($packageName)\$($packageName).MsiInstall.log`""
      validExitCodes= @(0, 3010, 1641)
      softwareName  = "legitest*"
      checksum = 'AF05C6B8A3739CC7AEA77A11DB989A75DAA7078017367FA844C95A616E03A828'
      checksumType = 'sha256'
      checksumType64 = 'sha256'
    Function Test-VsRegistry($registryPath, $registryProperty)
        $result = Get-ItemProperty $registryPath $registryProperty -ErrorAction SilentlyContinue
        if (($result -ne $null) -and ($result.InstallDir -ne $null) -and ($result.InstallDir.Length -gt 0))
            return $true
        return $false
    $isInstallLegiTest = $false
    $vs2012 = $false
    $vs2013 = $false
    $vs2015 = $false
    if ([IntPtr]::size -eq 8)
        $vs2012 = Test-VsRegistry("HKLM:\Software\WOW6432NODE\Microsoft\VisualStudio\11.0", "InstallDir")
        $vs2013 = Test-VsRegistry("HKLM:\Software\WOW6432NODE\Microsoft\VisualStudio\12.0", "InstallDir")
    	$vs2015 = Test-VsRegistry("HKLM:\Software\WOW6432NODE\Microsoft\VisualStudio\14.0", "InstallDir")
        if (($vs2012 -eq $false) -and 
            ($vs2013 -eq $false) -and
    		($vs2015 -eq $false))
            $isInstallLegiTest = $false
            $isInstallLegiTest = $true
        $vs2012 = Test-VsRegistry("HKLM:\Software\Microsoft\VisualStudio\11.0", "InstallDir")
        $vs2013 = Test-VsRegistry("HKLM:\Software\Microsoft\VisualStudio\12.0", "InstallDir")
    	$vs2015 = Test-VsRegistry("HKLM:\Software\Microsoft\VisualStudio\14.0", "InstallDir")
        if (($vs2012 -eq $false) -and 
            ($vs2013 -eq $false) -and
    		($vs2015 -eq $false))
            $isInstallLegiTest = $false
            $isInstallLegiTest = $true
    if ($isInstallLegiTest -eq $true)
        Install-ChocolateyVsixPackage $packageName $url
        throw "LegiTest requires Visual Studio 2012, 2013, 2015."
  • tools\chocolateyuninstall.ps1 Show
    $ErrorActionPreference = 'Stop';
    $packageName = 'legitest'
    $softwareName = 'legitest*'
    $installerType = 'VSIX' 
    $silentArgs = '/q'
    $validExitCodes = @(0, 1001)
    $uninstalled = $false
    $file = ''
    Uninstall-ChocolateyPackage -PackageName $packageName -FileType $installerType -SilentArgs "$silentArgs" -ValidExitCodes $validExitCodes -File "$file"

Virus Scan Results

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.


This package has no dependencies.

Package Maintainer(s)

Software Author(s)

  • Pragmatic Works Software


© 2016


Release Notes

LegiTest version 2017.3.2.612-beta

New Features

10820: LegiTest UX Improvements
  • "Wizard: Interactive Comparison" is now just "Interactive Comparison" in the context menu.
  • When adding a new connection from the Interactive Comparison wizard, the focus will start in the Connection Name box.
10825: Added Xml Comparison Assertion
11178: LegiTest Extension now supports Visual Studio 2017
  • Email [email protected] to request the installer that contains the Visual Studio 2017 supported version of the LegiTest Extension
11680: Added support for SQL Server 2017
11869: LegiTest Command Line can now push assemblies to the server.

Updated Features

10319: Comparison Manifests now work based on column name instead of column index
10925: Small numbers are now detected as more commonly used types


9248: Double clicking on the scroll bars within System Coverage adds selected item to target list
10923: "Wrong number of arguments provided" error when additional columns are added to test data source
11691: Previewing a query in Interactive Comparison fails when using a Data Driven variable.
11871: Adding two interactive comparisons in the same tests re-uses the same resource keys
12037: Using a reserved word (params, int, static, etc...) as a project name, prevents LegiTest from compiling

Version History

Version Downloads Last updated Status
LegiTest 2018.2.4.503 7317 Thursday, May 3, 2018 approved
LegiTest 2018.2.3.427 808 Saturday, April 28, 2018 approved
LegiTest 2018.2.3.412-beta 119 Thursday, April 12, 2018 approved
LegiTest 2018.2.2.302-beta 123 Friday, March 2, 2018 approved
LegiTest 2018.1.4.208 6122 Thursday, February 8, 2018 approved
LegiTest 2018.1.4.129-beta 136 Monday, January 29, 2018 approved
LegiTest 2018.1.3.122-beta 147 Monday, January 22, 2018 approved
LegiTest 2018.1.2.1206-beta 154 Wednesday, December 6, 2017 approved
LegiTest 2018.1.1.1030-beta 198 Monday, October 30, 2017 approved
Show More

Discussion for the LegiTest Package

Ground rules:

  • This discussion is only about LegiTest and the LegiTest 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 LegiTest, 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 uses cookies to enhance the user experience of the site.