-
Notifications
You must be signed in to change notification settings - Fork 120
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update regression test responses, expected results & artefacts
For scenarios in which the husband's income is less than the income limit, the
user is taken direct to the `husband_done` outcome. Since the income limit has
just been fixed, it has increased from £27,000 to £27,700. Therefore for the
scenarios in which the husband's income response is £27,001, the user will now
be taken to that outcome; whereas for those in which the husband's income is
£27,701, the user will continue to be taken to the subsequent questions.
The changes in the artefacts can be best explained by looking at an ASCII tree
of the files & directories before and after the changes in this commit:
$ tree test/artefacts/calculate-married-couples-allowance/yes/yes/1950-01-01
test/artefacts/calculate-married-couples-allowance/yes/yes/1950-01-01
├── 20000.txt
├── 27001.0
│ ├── no
│ │ └── 0.txt
│ ├── yes
│ │ ├── 10000.0
│ │ │ ├── 5000.0
│ │ │ │ └── 0.txt
│ │ │ └── 5000.html
│ │ └── 10000.html
│ └── yes.html
├── 27001.html
├── 27701.0
│ ├── no
│ │ └── 0.txt
│ └── yes
│ └── 10000.0
│ └── 5000.0
│ └── 0.txt
└── 50000.0
├── no
│ └── 0.txt
└── yes
└── 10000.0
└── 5000.0
└── 0.txt
$ tree test/artefacts/calculate-married-couples-allowance/yes/yes/1950-01-01
test/artefacts/calculate-married-couples-allowance/yes/yes/1950-01-01
├── 20000.txt
├── 27001.txt
├── 27701.0
│ ├── no
│ │ └── 0.txt
│ ├── yes
│ │ ├── 10000.0
│ │ │ ├── 5000.0
│ │ │ │ └── 0.txt
│ │ │ └── 5000.html
│ │ └── 10000.html
│ └── yes.html
├── 27701.html
└── 50000.0
├── no
│ └── 0.txt
└── yes
└── 10000.0
└── 5000.0
└── 0.txt
* The £20,000 & £50,000 scenarios stay the same - the former goes straight to an
outcome and the latter goes to the subsequent questions.
* The £27,001 scenarios collapse down to a single node, because it now goes
straight to an outcome.
* The £27,701 scenarios basically stay the same, although we now capture the
"Are you paying into a pension?" question page in this scenario and so it is
now named "27701.html" vs "27001.html".
Something very similar happesn for the highest earner scenarios:
$ tree test/artefacts/calculate-married-couples-allowance/yes/no
test/artefacts/calculate-married-couples-allowance/yes/no
├── 1955-01-01
│ ├── 20000.txt
│ ├── 27001.0
│ │ ├── no
│ │ │ └── 0.txt
│ │ └── yes
│ │ └── 10000.0
│ │ └── 5000.0
│ │ └── 0.txt
│ ├── 27701.0
│ │ ├── no
│ │ │ └── 0.txt
│ │ └── yes
│ │ └── 10000.0
│ │ └── 5000.0
│ │ └── 0.txt
│ └── 55000.0
│ ├── no
│ │ └── 0.txt
│ └── yes
│ └── 10000.0
│ └── 5000.0
│ └── 0.txt
└── 1955-01-01.html
$ tree test/artefacts/calculate-married-couples-allowance/yes/no
test/artefacts/calculate-married-couples-allowance/yes/no
├── 1955-01-01
│ ├── 20000.txt
│ ├── 27001.txt
│ ├── 27701.0
│ │ ├── no
│ │ │ └── 0.txt
│ │ └── yes
│ │ └── 10000.0
│ │ └── 5000.0
│ │ └── 0.txt
│ └── 55000.0
│ ├── no
│ │ └── 0.txt
│ └── yes
│ └── 10000.0
│ └── 5000.0
│ └── 0.txt
└── 1955-01-01.html
All the regression tests are passing at this point, so I've also updated the
checksums.- Loading branch information
1 parent
fa9716c
commit b225746
Showing
10 changed files
with
20 additions
and
180 deletions.
There are no files selected for viewing
19 changes: 0 additions & 19 deletions
19
...ts/calculate-married-couples-allowance/yes/no/1955-01-01/27001.0/yes/10000.0/5000.0/0.txt
This file was deleted.
Oops, something went wrong.
File renamed without changes.
19 changes: 0 additions & 19 deletions
19
...s/calculate-married-couples-allowance/yes/yes/1950-01-01/27001.0/yes/10000.0/5000.0/0.txt
This file was deleted.
Oops, something went wrong.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters