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

This is a prerelease version of LegiTest.

LegiTest

2015.4.1-beta1

There are no package test results for this package

This package is exempt from moderation. While it is likely safe for you, there is more risk involved.

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.

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

C:\> choco install legitest --version 2015.4.1-beta1 --pre

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

C:\> choco upgrade legitest --version 2015.4.1-beta1 --pre

Files

Hide
  • tools\chocolateyinstall.ps1 Show
    $ErrorActionPreference = 'Stop';
    
    $packageName= 'legitest'
    $toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
    $url        = 'https://www.pragmaticworks.com/Downloads/LegiTest/BETA_LegiTest_2015.4.1.1029.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*'
    }
    
    Install-ChocolateyVsixPackage $packageName $url
    
  • 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"
    
  • tools\ReadMe.md Show
    ## Summary
    How do I create packages? See https://github.com/chocolatey/choco/wiki/CreatePackages
    
    If you are submitting packages to the community feed (https://chocolatey.org)
    always try to ensure you have read, understood and adhere to the create
    packages wiki link above.
    
    ## Automatic Packages?
    Consider making this package an automatic package, for the best 
    maintainability over time. Read up at https://github.com/chocolatey/choco/wiki/AutomaticPackages
    
    ## Shim Generation
    Any executables you include in the package or download (but don't call 
    install against using the built-in functions) will be automatically shimmed.
    
    This means those executables will automatically be included on the path.
    Shim generation runs whether the package is self-contained or uses automation 
    scripts. 
    
    By default, these are considered console applications. 
    
    If the application is a GUI, you should create an empty file next to the exe 
    named 'name.exe.gui' e.g. 'bob.exe' would need a file named 'bob.exe.gui'.
    See https://github.com/chocolatey/choco/wiki/CreatePackages#how-do-i-set-up-batch-redirects-for-applications-that-have-a-gui
    
    If you want to ignore the executable, create an empty file next to the exe 
    named 'name.exe.ignore' e.g. 'bob.exe' would need a file named 
    'bob.exe.ignore'. 
    See https://github.com/chocolatey/choco/wiki/CreatePackages#how-do-i-exclude-executables-from-getting-batch-redirects
    
    ## Self-Contained? 
    If you have a self-contained package, you can remove the automation scripts 
    entirely and just include the executables, they will automatically get shimmed, 
    which puts them on the path. Ensure you have the legal right to distribute 
    the application though. See https://github.com/chocolatey/choco/wiki/Legal. 
    
    You should read up on the Shim Generation section to familiarize yourself 
    on what to do with GUI applications and/or ignoring shims.
    
    ## Automation Scripts
    You have a powerful use of Chocolatey, as you are using PowerShell. So you
    can do just about anything you need. Choco has some very handy built-in 
    functions that you can use, these are sometimes called the helpers.
    
    ### Built-In Functions
    https://github.com/chocolatey/choco/wiki/HelpersReference
    
    A note about a couple:
    * Get-BinRoot - this is a horribly named function that doesn't do what new folks think it does. It gets you the 'tools' root, which by default is set to 'c:\tools', not the chocolateyInstall bin folder. 
    * Install-BinFile - used for non-exe files - executables are automatically shimmed...
    * Uninstall-BinFile - used for non-exe files - executables are automatically shimmed
    
    ### Getting package specific information
    Use the package parameters pattern - see https://github.com/chocolatey/choco/wiki/How-To-Parse-PackageParameters-Argument
    
    ### Need to mount an ISO?
    https://github.com/chocolatey/choco/wiki/How-To-Mount-An-Iso-In-Chocolatey-Package
    
    
    ### Environment Variables
    Chocolatey makes a number of environment variables available (You can access any of these with $env:TheVariableNameBelow):
    
     * TEMP = Overridden to the CacheLocation, but may be the same as the original TEMP folder
     * ChocolateyInstall = Top level folder where Chocolatey is installed
     * chocolateyPackageName = The name of the package, equivalent to the id in the nuspec (0.9.9+)
     * chocolateyPackageVersion = The version of the package, equivalent to the version in the nuspec (0.9.9+)
     * chocolateyPackageFolder = The top level location of the package folder
    
    #### Advanced Environment Variables
    The following are more advanced settings:
    
     * chocolateyPackageParameters = (0.9.8.22+)
     * CHOCOLATEY_VERSION = The version of Choco you normally see. Use if you are 'lighting' things up based on choco version. (0.9.9+)
        - Otherwise take a dependency on the specific version you need. 
     * chocolateyForceX86 = If available and set to 'true', then user has requested 32bit version. (0.9.9+)
        - Automatically handled in built in Choco functions. 
     * OS_PLATFORM = Like Windows, OSX, Linux. (0.9.9+)
     * OS_VERSION = The version of OS, like 6.1 something something for Windows. (0.9.9+)
     * OS_NAME = The reported name of the OS. (0.9.9+)
     * IS_PROCESSELEVATED = Is the process elevated? (0.9.9+)
     
    #### Experimental Environment Variables
    The following are experimental or use not recommended:
    
     * OS_IS64BIT = This may not return correctly - it may depend on the process the app is running under (0.9.9+)
     * CHOCOLATEY_VERSION_PRODUCT = the version of Choco that may match CHOCOLATEY_VERSION but may be different (0.9.9+)
        - it's based on git describe
     * IS_ADMIN = Is the user an administrator? But doesn't tell you if the process is elevated. (0.9.9+)
     * chocolateyInstallOverride = Not for use in package automation scripts. (0.9.9+)
     * chocolateyInstallArguments = the installer arguments meant for the native installer. You should use chocolateyPackageParameters intead. (0.9.9+)
    
    

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.

Dependencies

This package has no dependencies.

Package Maintainer(s)

Software Author(s)

  • Pragmatic Works Software

Copyright

© 2015

Tags

Release Notes

Pragmatic Workbench 2015.4.1-beta1 Release Notes

Please visit LegiTest's online documentation for the latest release notes: http://help.pragmaticworks.com/legitest/.

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
Chocolatey.org uses cookies to enhance the user experience of the site.
Ok