Testing against dev builds

Open

#31 opened on Jun 15, 2015 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 25/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Stale
Tech stack: yaml
Domain: ci-cd, testing-qa

Research direction

Start with .travis.yml and investigate Travis CI's secret-value settings, then review how the dev build is downloaded and installed. Done means CI can securely provide a valid license in the expected location and execute tests against the dev build without exposing the license.

Written by the indexing model from the issue text.

Description

It's currently not possible to test against the dev builds. This would require:

Downloading and installing the dev build (easy on Windows).
Somehow providing an interface to place a valid license in the correct location to allow execution of the dev build.

Travis CI has a kind of "secret value setting" thing where you can provide secret information that is not part of .travis.yml, but I don't exactly remember how it works, nor have I ever used it.

Dominant language: Python
Stars: 113
Forks: 32
PR merge metrics: No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.