LegiTest

This is not the latest version of LegiTest available.

2016.4.4 | Updated: 10/25/2016

Downloads:

96,931

Downloads of v 2016.4.4:

213

Software Author(s):

  • Pragmatic Works Software

LegiTest 2016.4.4

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: 2016.4.4
    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  '2016.4.4'
  source   'STEP 3 URL'
end

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


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

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


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

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


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

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


salt '*' chocolatey.install legitest version="2016.4.4" 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 by moderator gep13 on 10/27/2016.

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        = 'http://download.pragmaticworks.com/release/2016.4/LegiTest_2016.4.4.1024.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*"
}

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 134 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 152 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 213 Monday, October 30, 2017 Approved

LegiTest version 2016.4.4

New Features

4776: Query Editor supports Azure SQL DB
  • The query editor built in to LegiTest now supports connections to Azure SQL DB
4852: Resource key usages are now automatically remapped if a resource key is renamed
6729: Usability improvements for the Annotations UI
  • Annotation type creation pane is now a separate configuration page.
  • The content field supports Markdown for richer formatting when displayed on the server.
  • The content field size has been increased, and it now supports multiple lines.
  • Annotations for each test / group are listed under the test / group instead of a test-suite level pane.
6767: Updated comparison editor UI
  • Added an indicator that shows when code completion is available
  • Added an indicator that shows when the editor is connected
  • Added a Run Query toolbar button to each query editor
7345: Increased detail within error reports for Grid Validation assertions
  • The Grid Validation assertion now reports row details in a similar manner to the Grid Comparison assertion
7377: Data driven testing now supported
  • Tests can now be configured to use a data set or grid as input, so that the test executes once for each row in the data set.
  • Execute the same test logic for a large number of scenarios very easily
  • Use data from any ADO.NET source, SalesForce or REST
7855: Improved validation warnings when re-using a resource key name

Updated Features

4768: IntelliSense now available for grid collection asset editor
5498: Validation assertions can now expect empty grids
6215: SSAS Process Item Actions now include option to fail on process failure
6811: Comparison Manifest editor now shows the configured grids for actual and expected

Fixes

4774: Query Editor picks arbitrary Sql connection for editing
4904: Query Editor errors are less intrusive
6194: Editing a comparison column mapping for an invalid column results in a modal error dialog
6198: VSIX Uninstaller isn't removing extensions during uninstall process
6625: Visual Studio 2012 crashes when using "Format SQL" button
6727: SalesForce Query doesn't honor parameters when providing columns for comparison / validation
6728: Validation Manifest that references SF Query with no rows doesn't allow editing of validation columns
6731: Executing the LegiTest commandline executable with no parameters throws an unhandled exception
6743: Help website has grammatical and spelling errors
6763: Interactive Comparison won't let you finish with an incomplete test
6764: The Interactive Comparison editor doesn't evaluate parameters defined outside of Test Suite Parameters
6812: Checking the Show Equal Rows option doesn't trigger an automatic reload
7326: Syncing does not update annotation description
7390: SalesForce actions do not return results if they contain three part column names
7397: Elements with default editor do not save values when another element is selected
7846: Execute REST actions do not parameterize properties
7904: Fixed issue with SSRS report calling Parameters


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