Add a manual trigger with the ability to set env vars about alkiln HOT 6 CLOSED

Discussing allowing the following inputs:

1. language: Pick just one language to run. How do we make sure that 'default' will run the default language without error? Can probably use it to set environment variables. Alternatively, an if in the workflow or in the test?
2. extra_languages: A list of comma separated languages to test. Why not? Nothing should ever not be a list!
3. url: Specify a different url to test at (INTERVIEW_URL environment variable) (test_url? interview_url? Do not run setup or takedown when this is set)
4. tag: Once we have tags figured out, test only tests with that tag.
5. filepath: Pick one specific test file. Would probably affect the file path given as the argument to the script. Can that script use environment variables? [Maybe allow a glob?] [Maybe tags would be better than filepaths]

Should all of these be able to be env variables that are then overridden by these manual variables?

Other ideas/thoughts?

from alkiln.

extra_languages might be a better name than languages

from alkiln.

• Manual trigger has been added.
• extra_languages is now available, though language-agnostic functionality is not quite ready.

from alkiln.

extra_languages has been added.

from alkiln.

Remaining:

• url
• tags
• fileglob (?)

from alkiln.

At this point, we have decided against adding these other env vars.

• tags: Authors manage this now in their workflow file
• languages: Can be controlled with a cucumber Examples block in a Scenario Outline for the test. We'll see if it's possible to use a Background action so authors can avoid writing those examples in every test.
• url Can be given on a per-Scenario, or even per-Step, basis.
• filepath: Actually better taken care of by tags

from alkiln.