Downloads:

1,082

Downloads of v 1.2.1.1:

737

Last Update:

14 Feb 2017

Package Maintainer(s):

Software Author(s):

  • James Bach

Tags:

pairwise testing

All Pairs

1.2.1.1 | Updated: 14 Feb 2017

Downloads:

1,082

Downloads of v 1.2.1.1:

737

Maintainer(s):

Software Author(s):

  • James Bach

All Pairs 1.2.1.1

Some Checks Have Failed or Are Not Yet Complete

1 Test Passing and 1 Failing Test


Validation Testing Passed


Verification Testing Failed

Details

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

>

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

>

To uninstall All Pairs, 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 allpairs -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 allpairs -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 allpairs installed
  win_chocolatey:
    name: allpairs
    state: present
    version: 1.2.1.1
    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 'allpairs' do
  action    :install
  version  '1.2.1.1'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: allpairs,
    Version: 1.2.1.1,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller allpairs
{
   Name     = 'allpairs'
   Ensure   = 'Present'
   Version  = '1.2.1.1'
   Source   = 'STEP 3 URL'
}

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


package { 'allpairs':
  provider => 'chocolatey',
  ensure   => '1.2.1.1',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install allpairs version="1.2.1.1" 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.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator AdmiringWorm on 18 Feb 2017.

Description

Let's say you must test something that involves a lot of different variables. Configuration testing is like that: different printers, different print options, different documents. Who knows what combination will fail? But you can't try all combinations of all variables together, because that would be too many tests. So instead, you could create tests that pair each value of each of the variables with each value of each other variable at least once. Allpairs is a tool I wrote that will find a reasonably small set of test cases to satisfy that coverage standard. For instance, to try all combinations of 10 variables with ten values each would require 10,000,000,000 test cases. Allpairs only requires 177 cases.


tools\chocolateyInstall.ps1
$tools = Split-Path $MyInvocation.MyCommand.Definition
$content = Join-Path (Split-Path $tools) 'content'

Install-ChocolateyZipPackage `
    -PackageName 'allpairs' `
    -Url 'http://www.satisfice.com/tools/pairs.zip' `
    -Checksum 'A50999058F73AE75CFD32BDDC3169B300C8210F8547FFF0B93332F738737CAC7' `
    -ChecksumType 'SHA256' `
    -UnzipLocation $content

Log in or click on link to see number of positives.

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
All Pairs 1.2.1 345 Monday, March 2, 2015 Approved

This package has no dependencies.

Discussion for the All Pairs Package

Ground Rules:

  • This discussion is only about All Pairs and the All Pairs 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 All Pairs, 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