-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathEpic1_AutomatedRegressionSuite.feature
More file actions
90 lines (77 loc) · 5.78 KB
/
Epic1_AutomatedRegressionSuite.feature
File metadata and controls
90 lines (77 loc) · 5.78 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
Feature: Epic1_AutomatedRegressionSuite
DTOSS Regression TEST PACK.
Background:
Given the database is cleaned of all records for NHS Numbers: 1111110662, 2222211794,2312514176,2612314172,2612514171
And the application is properly configured
@DTOSS-7583 @Regression
Scenario: Verify NHS data propagation across participant tables after file upload for ADD record
Given file <FileName> exists in the configured location for "Add" with NHS numbers : <NhsNumbers>
When the file is uploaded to the Blob Storage container
Then verify the NHS numbers in Participant_Management and Participant_Demographic table should match the file data
Examples:
| FileName | RecordType | NhsNumbers |
| ADD_2_RECORDS_-_CAAS_BREAST_SCREENING_COHORT.parquet | Add | 1111110662, 2222211794 |
@DTOSS-7583 @Regression
Scenario: Verify NHS data propagation across participant tables after file upload for AMENDED record
Given file <AddFileName> exists in the configured location for "Add" with NHS numbers : <NhsNumbers>
And the file is uploaded to the Blob Storage container
And the NHS numbers in the database should match the file data
And file <AmendedFileName> exists in the configured location for "Amended" with NHS numbers : <NhsNumbers>
When the file is uploaded to the Blob Storage container
Then verify the NhsNumbers in Participant_Management table should match <RecordType>
And the Participant_Demographic table should match the <AmendedGivenName> for the NHS Number
Examples:
| AddFileName | AmendedFileName | NhsNumbers | AmendedGivenName | RecordType |
| ADD1_1B8F53_-_CAAS_BREAST_SCREENING_COHORT.parquet | AMENDED1_1B8F53_-_CAAS_BREAST_SCREENING_COHORT.parquet | 2312514176 | AMENDEDNewTest1 | Amended |
@DTOSS-7584 @Regression
Scenario: Confirm NHS Number Count Integrity Across Participant Tables After Processing for ADD record
Given file <FileName> exists in the configured location for "Add" with NHS numbers : <NhsNumbers>
When the file is uploaded to the Blob Storage container
Then the NHS Number should have exactly 1 record in Participant_Management
And the NHS Number should have exactly 1 record in Participant_Demographic
Examples:
| FileName | RecordType | NhsNumbers |
| ADD_2_RECORDS_-_CAAS_BREAST_SCREENING_COHORT.parquet | Add | 1111110662, 2222211794 |
@DTOSS-7584 @Regression
Scenario: Confirm NHS Number Count Integrity Across Participant Tables After Processing for AMENDED record
Given file <AddFileName> exists in the configured location for "Add" with NHS numbers : <NhsNumbers>
And the file is uploaded to the Blob Storage container
And the NHS numbers in the database should match the file data
And file <AmendedFileName> exists in the configured location for "Amended" with NHS numbers : <NhsNumbers>
When the file is uploaded to the Blob Storage container
Then the NHS Number should have exactly 1 record in Participant_Management
And the NHS Number should have exactly 1 record in Participant_Demographic
Examples:
| AddFileName | AmendedFileName | NhsNumbers |
| ADD1_1B8F53_-_CAAS_BREAST_SCREENING_COHORT.parquet | AMENDED1_1B8F53_-_CAAS_BREAST_SCREENING_COHORT.parquet | 2312514176 |
@DTOSS-7585 @Regression
Scenario: Verify exception records doesn't end up in Participant_Demographic and Participant_Management table for ADD record
Given file <AddFileName> exists in the configured location for "Add" with NHS numbers : <NhsNumbers>
When the file is uploaded to the Blob Storage container
Then the Exception table should contain the below details for the NHS Number
| FieldName | FieldValue |
| RULE_ID | 36 |
| RULE_DESCRIPTION | Invalid primary care provider GP practice code |
Then the NHS Number should have exactly 1 record in Participant_Management
And the NHS Number should have exactly 1 record in Participant_Demographic
And the NHS Number should have exactly 0 record in Cohort_Distribution table
Examples:
| AddFileName | NhsNumbers |
| Exception_1B8F53_-_CAAS_BREAST_SCREENING_COHORT.parquet | 2612314172 |
@DTOSS-7585 @Regression
Scenario: Verify exception records doesn't end up in Participant_Demographic and Participant_Management table for AMENDED record
Given file <AddFileName> exists in the configured location for "Add" with NHS numbers : <NhsNumbers>
And the file is uploaded to the Blob Storage container
And the NHS numbers in the database should match the file data
And file <AmendedFileName> exists in the configured location for "Amended" with NHS numbers : <NhsNumbers>
When the file is uploaded to the Blob Storage container
Then the Exception table should contain the below details for the NHS Number
| FieldName | FieldValue |
| RULE_ID | 17 |
| RULE_DESCRIPTION | Date of birth invalid |
Then the NHS Number should have exactly 1 record in Participant_Management
And the NHS Number should have exactly 1 record in Participant_Demographic
And the NHS Number should have exactly 1 record in Cohort_Distribution table
Examples:
| AddFileName | AmendedFileName | NhsNumbers |
| ADD_1B8F53_-_CAAS_BREAST_SCREENING_COHORT.parquet | AMENDED_1B8F53_-_CAAS_BREAST_SCREENING_COHORT.parquet | 2612514171 |