LegiTest

This is a prerelease version of LegiTest.

2017.4.3.1010-beta | Updated: 10/10/2017

Downloads:

96,691

Downloads of v 2017.4.3.1010-beta:

195

Software Author(s):

  • Pragmatic Works Software

LegiTest 2017.4.3.1010-beta

This is a prerelease version of LegiTest.

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

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


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

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


cChocoPackageInstaller legitest
{
   Name     = 'legitest'
   Ensure   = 'Present'
   Version  = '2017.4.3.1010-beta'
   Source   = 'STEP 3 URL'
}

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


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

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


salt '*' chocolatey.install legitest version="2017.4.3.1010-beta" 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 10/10/2017.

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/prerelease/BETA/2017.4/BETA_LegiTest_2017.4.3.1010.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 = 'A6231CD4EC975CA728F153BEEB7193ED12D89C4938373FA656A0104701A63209'
  checksumType = 'sha256'
  checksum64 = 'QTYyMzFDRDRFQzk3NUNBNzI4RjE1M0JFRUI3MTkzRUQxMkQ4OUM0OTM4MzczRkE2NTZBMDEwNDcwMUE2MzIwOQ=='
  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 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 2017.4.3.1010-beta

New Features

5476: Improved multi-developer experience
  • Assets can now be defined at the project level
  • Added ability to have single groups in single files, enabling better sharing
  • Added project-level parameter files to simplify configuration across a project
  • Added project-level server integration to enable simpler and more consistent deployment
9822: Reduced runtime dependency footprint for LegiTest
  • Less DLL references are now required for some testing patterns
11951: Added error inspector for looking at warnings at the group/test level
  • Warning tooltips are also enhanced with extra detail
13116: Runtime dependencies can now be resolved via NuGet
  • Most of the runtime dependencies of LegiTest tests can now be resolved via NuGet, making deployment on build servers much easier
13435: Generated file names for asset content files are shorter
  • Names of existing assets will be shortened upon opening the test suite / group that contains them.
13454: Added ability to define test framework type at project level
  • Framework type is now defined at the project level, instead of for individual suites/groups
13480: Suites, Groups, Settings and Asset files now have appropriate icons
13502: Added ability to ignore tasks by name in SSIS Wizard
  • Added ability to use wildcards to ignore tasks by name - e.g. SSISOps

Updated Features

8753: REST assets now include a "Number of Retries" option that controls the amount of connection attempts upon failure
11156: Added help overlay to the query editor
13492: Improved warning message within SSIS Package Reference asset when pointing to a newer SSIS version

Fixes

12021: DOC xPress connector and System Coverage panel give no warning when server is unlicensed
12414: Comparison for Validation Manifest are run in reverse of what the UI displays
13060: Package Reference Asset throws an SSISCatalogPackageNotFoundException error when a folder is selected
13072: ReadHistoricalResultsAction can display an interactive dialog during test execution
13093: LegiTest does not publish to server all needed assemblies when using SSIS Packages Reference
13098: LegiTest suites / groups do not function correctly in project sub-folders
13100: LegiTest tests will fail on a data driven run if the server fails and 'fail on server failure' is not checked
13104: Renaming a Suite or Group does not delete the old output folder
13120: Actual and Expected values are being flipped on integer comparison when pushing results to server.
13458: New "LegiTest Project - NUnit" projects do not include a NuGet reference to NUnitTestAdapter
13935: Within Connection Asset, clicking the Test Connection throws InvalidOperationException if Connection String is empty
13936: "The type or namespace name 'Dictionary<,>' could not be found" when generating a LegiTestGroup without any tests
13987: "Member names cannot be the same as their enclosing type" when a test is named the same as its group
13993: Publishing a Data Driven test that uses a Delimited Content asset misses publishing certain assemblies
14000: Data Driven tests containing nullable values can throw ArgumentException
14033: SSIS Package Wizard throws an InvalidDataException when selecting a package that has a higher SSIS version
14551: Interactive Comparison throws "Comparison no longer exists" error when mapping key columns with different names


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