Open plocket opened 3 years ago
I think Background
might be better to [make use of] its current functionality - running some steps before each Scenario in a file. [For example, allow dev to set the foundation of a story table that they can build on later. I'm not sure how to then differentiate it from tables they add later, or to let them make a table that's not based on that base story table. It's complicated. We can start with just a base/foundational table, though.]
The pre-release for the story table Background step is out. Currently for v3 on branch https://github.com/SuffolkLITLab/ALKiln/tree/75_background_table_v3. Here are some general instructions for trying it out:
To start with, we're trying pre-release version 3.3.0-background-table.2
. If you're not using a GitHub secret:
ALKILN_VERSION: "3.3.0-background-table.2"
Depends on the setup. Basically need to make sure that we can pull in a pre-release version of the lib.
If the repo has its own package.json, just update version of docassemble-cucumber to the pre-release version.
If the repo only has the workflow file, no package.json:
step
that uses
suffolkLITLab/ALKiln@releases/v3
. ALKILN_VERSION: "x.x.x..."
or
secrets.ALKILN_VERSION
inside the brackets:
ALKILN_VERSION: "${{ secrets.ALKILN_VERSION }}"
You'll need to know the id of the last page you want to get to for each Scenario.
Background:
Given I always have this data:
Background:
Given I always have this data:
| var | value | trigger |
| users[0].name.first | Uli | users[0].name.first |
| users[0].name.last | User1 | users[0].name.first |
And I get to "final question id" with the background data
Example:
Scenario: index.yml runs
And the maximum seconds for each Step in this Scenario is 800
And I wait 800 seconds
Given I start the interview at "index.yml"
And I get to "final question id" with the background data
Edit: Example here while the branch is alive: https://github.com/SuffolkLITLab/ALKiln/blob/75_background_table_v3/tests/features/observation_steps.feature#L6-L17 then https://github.com/SuffolkLITLab/ALKiln/blob/75_background_table_v3/tests/features/observation_steps.feature#L45-L48
I've rebased this to be on version 4 now, still leaving the old branch in case there's still something useful.
Can't make a pre-release personally, but I'll personally try to test it a little bit, and if I don't run into any issues, or confusing parts, I'll make a PR with this code.
In combination with human languages
Proposed: Each file contains only one 'story' set up as a cucumber
Background
. EachScenario
in it just sets a language for the test. We handle skipping or testing languages with cucumbertag
s.'Story' here means one set of user data (has 3 children, lives in an apartment, lives out of state, etc.) Usually this might be called a 'scenario', but cucumber uses that term for specific functionality that is also part of this discussion.
Pros
Cons
Questions