LegiTest

This is not the latest version of LegiTest available.

2018.1.4.208 | Updated: 2/8/2018

Downloads:

95,998

Downloads of v 2018.1.4.208:

6,141

Software Author(s):

  • Pragmatic Works Software

LegiTest 2018.1.4.208

This is not the latest version of LegiTest 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 LegiTest, run the following command from the command line or from PowerShell:

>

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

>

To uninstall LegiTest, 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 legitest -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 legitest -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 legitest installed
  win_chocolatey:
    name: legitest
    state: present
    version: 2018.1.4.208
    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 'legitest' do
  action    :install
  version  '2018.1.4.208'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: legitest,
    Version: 2018.1.4.208,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller legitest
{
   Name     = 'legitest'
   Ensure   = 'Present'
   Version  = '2018.1.4.208'
   Source   = 'STEP 3 URL'
}

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


package { 'legitest':
  provider => 'chocolatey',
  ensure   => '2018.1.4.208',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install legitest version="2018.1.4.208" 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 2/9/2018.

Description

LegiTest

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.

Easy-to-Use

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.

Extensible

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.


tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';

$packageName= 'legitest'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = 'https://download.pragmaticworks.com/release/2018.1/LegiTest_2018.1.4.208.vsix'

$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 = 'B0A8DF6BC55A38F67638DD7FF2A4E713A14B5517F593CA0EC8323B48B519B2DE'
  checksumType = 'sha256'
  checksum64 = 'QjBBOERGNkJDNTVBMzhGNjc2MzhERDdGRjJBNEU3MTNBMTRCNTUxN0Y1OTNDQTBFQzgzMjNCNDhCNTE5QjJERQ=='
  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
    }
    else
    {
        $isInstallLegiTest = $true
    }
}
else
{
    $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
    }
    else
    {
        $isInstallLegiTest = $true
    }
}

if ($isInstallLegiTest -eq $true)
{
    Install-ChocolateyVsixPackage $packageName $url
}
else
{
    throw "LegiTest requires Visual Studio 2012, 2013, 2015."
}
tools\chocolateyuninstall.ps1
$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"

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
LegiTest 2018.2.4.503 7335 Thursday, May 3, 2018 Approved
LegiTest 2018.2.3.427 817 Saturday, April 28, 2018 Approved
LegiTest 2018.2.3.412-beta 133 Thursday, April 12, 2018 Approved
LegiTest 2018.2.2.302-beta 143 Friday, March 2, 2018 Approved
LegiTest 2018.1.4.208 6141 Thursday, February 8, 2018 Approved
LegiTest 2018.1.4.129-beta 151 Monday, January 29, 2018 Approved
LegiTest 2018.1.3.122-beta 158 Monday, January 22, 2018 Approved
LegiTest 2018.1.2.1206-beta 168 Wednesday, December 6, 2017 Approved
LegiTest 2018.1.1.1030-beta 211 Monday, October 30, 2017 Approved

LegiTest version 2018.1.4.208

New Features

5497: Validation and Comparison manifests now support regular expression matching and asymmetric tolerances
  • A new match type of 'RegexMatch' can be used to match an expected regular expression pattern against an actual value
  • Percentage and fixed tolerance comparisons can now be set to use asymmetric tolerance values for specific ranges
11057: LegiTest now auto selects resources / assets when possible
13437: When re-publishing an assembly that is in the recycle bin on the server the assemblies are removed from the trash
14542: Visual Studio's test output console now includes LegiTest parameter information
14663: LegiTest extensions now support initializing logging through external configuration files
14715: Added support for Recipes
  • Recipes allow reusable test patterns to be quickly and easily turned into tests, allowing for tests to be created with very little knowledge of unit testing in general
  • Several recipes are available - including a uniqueness validation, range check, standard deviation validation etc
15190: Added 'Value Comparison' assertion
  • Value comparison replaces the 'Integer Comparison' and 'Scalar Comparison' assertions
  • Easier configuration for validating a single scalar value
  • Wider array of operators for comparison against multiple types
15191: Added 'Expression' assertion
  • Expression assertion allows LegiTest filter expressions to assert on single or multiple scalar values
  • Use complex combinational logic to verify resource values
  • Familiar SQL-like syntax for comparison and logical combination through AND / OR
15671: Load Text File action
  • The Load Text File action allows users the ability to load the content of any text file into a resource for later use

Updated Features

14583: Help Documentation now includes a Frequently Asked Question including detailed code samples for one-time use parameter values

Fixes

13467: 'Move Up' / 'Move Down' moves all tests to the bottom of the list
13901: Exception messages in Group Setup and Teardown are difficult to troubleshoot
13972: Compiler warning in generated projects: Architecture mismatch between MSIL and x86
13973: LegiTest does not parse user defined parameter syntax in Data Driven test queries
13978: Enabling an empty data-driven source causes unclear compilation error
14562: Within Data Driven Source, the "Edit Filter" and "Edit Asset" buttons for File Handling sources do not do anything
14626: Validation Manifest configured with invalid grid provider crashes Visual Studio on column load
15116: Project Level Asset file doesn't get marked as dirty in VS after changes
15129: LegiTest Rest Connection/Query Headers do not replace parameter syntax
15134: Legitest: "Object cannot be cast from DBNull to other types" error in Legacy Test Suites
15178: Fixed Width File Reference asset throws "Could not detect file format value cannot be null. Parameter name: values"
15252: Tests targeting NUnit error with BadImageFormatException when run via LegiTest Runner
15629: Parameter replacement does not work within the filter of a Data Driven Directory Reference
15654: Project level connection assets with parameterized connection strings do not work in all scenarios
15657: Value Comparison fails when ResourceKey contains ( or )
15658: Comparison Manifest does not recognize global connection assets


This package has no dependencies.

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