|
1 | 1 | @Update_Batch_Feature @functional |
2 | 2 | Feature: Create the immunization event for a patient through batch file and update the record from batch or Api calls |
3 | 3 |
|
4 | | -@smoke |
5 | | -@delete_cleanup_batch @vaccine_type_MMR @supplier_name_TPP |
6 | | -Scenario: Update immunization event for a patient through batch file |
7 | | - Given batch file is created for below data as full dataset and each record has a valid update record in the same file |
8 | | - | patient_id | unique_id | |
9 | | - | Random | Valid_NhsNumber | |
10 | | - | InvalidInPDS | InvalidInPDS_NhsNumber| |
11 | | - | SFlag | SFlag_NhsNumber | |
12 | | - | Mod11_NHS | Mod11_NhSNumber | |
13 | | - | OldNHSNo | OldNHSNo | |
14 | | - When batch file is uploaded in s3 bucket |
15 | | - Then file will be moved to destination bucket and inf ack file will be created |
16 | | - And inf ack file has success status for processed batch file |
17 | | - And bus ack files will be created |
18 | | - And CSV bus ack will not have any entry of successfully processed records |
19 | | - And Json bus ack will only contain file metadata and no failure record entry |
20 | | - And Audit table will have correct status, queue name and record count for the processed batch file |
21 | | - And The imms event table will be populated with the correct data for 'updated' event for records in batch file |
22 | | - And The delta table will be populated with the correct data for all created records in batch file |
23 | | - And The delta table will be populated with the correct data for all updated records in batch file |
| 4 | + @smoke |
| 5 | + @delete_cleanup_batch @vaccine_type_MMR @supplier_name_TPP |
| 6 | + Scenario: Update immunization event for a patient through batch file |
| 7 | + Given batch file is created for below data as full dataset and each record has a valid update record in the same file |
| 8 | + | patient_id | unique_id | |
| 9 | + | Random | Valid_NhsNumber | |
| 10 | + | InvalidInPDS | InvalidInPDS_NhsNumber | |
| 11 | + | SFlag | SFlag_NhsNumber | |
| 12 | + | Mod11_NHS | Mod11_NhSNumber | |
| 13 | + | OldNHSNo | OldNHSNo | |
| 14 | + When batch file is uploaded in s3 bucket |
| 15 | + Then file will be moved to destination bucket and inf ack file will be created |
| 16 | + And inf ack file has success status for processed batch file |
| 17 | + And bus ack files will be created |
| 18 | + And CSV bus ack will not have any entry of successfully processed records |
| 19 | + And Json bus ack will only contain file metadata and no failure record entry |
| 20 | + And Audit table will have correct status, queue name and record count for the processed batch file |
| 21 | + And The imms event table will be populated with the correct data for 'updated' event for records in batch file |
| 22 | + And The delta table will be populated with the correct data for all created records in batch file |
| 23 | + And The delta table will be populated with the correct data for all updated records in batch file |
24 | 24 |
|
25 | | -@Delete_cleanUp @vaccine_type_ROTAVIRUS @patient_id_Random @supplier_name_EMIS |
26 | | -Scenario: Verify that the API vaccination record will be successful updated by batch file upload |
27 | | - Given I have created a valid vaccination record through API |
28 | | - And The delta and imms event table will be populated with the correct data for api created event |
29 | | - When An update to above vaccination record is made through batch file upload |
30 | | - And batch file is uploaded in s3 bucket |
31 | | - Then file will be moved to destination bucket and inf ack file will be created |
32 | | - And inf ack file has success status for processed batch file |
33 | | - And bus ack files will be created |
34 | | - And CSV bus ack will not have any entry of successfully processed records |
35 | | - And Json bus ack will only contain file metadata and no failure record entry |
36 | | - And Audit table will have correct status, queue name and record count for the processed batch file |
37 | | - And The imms event table will be populated with the correct data for 'updated' event for records in batch file |
38 | | - And The delta table will be populated with the correct data for all updated records in batch file |
| 25 | + @Delete_cleanUp @vaccine_type_ROTAVIRUS @patient_id_Random @supplier_name_EMIS |
| 26 | + Scenario: Verify that the API vaccination record will be successful updated by batch file upload |
| 27 | + Given I have created a valid vaccination record through API |
| 28 | + And The delta and imms event table will be populated with the correct data for api created event |
| 29 | + When An update to above vaccination record is made through batch file upload |
| 30 | + And batch file is uploaded in s3 bucket |
| 31 | + Then file will be moved to destination bucket and inf ack file will be created |
| 32 | + And inf ack file has success status for processed batch file |
| 33 | + And bus ack files will be created |
| 34 | + And CSV bus ack will not have any entry of successfully processed records |
| 35 | + And Json bus ack will only contain file metadata and no failure record entry |
| 36 | + And Audit table will have correct status, queue name and record count for the processed batch file |
| 37 | + And The imms event table will be populated with the correct data for 'updated' event for records in batch file |
| 38 | + And The delta table will be populated with the correct data for all updated records in batch file |
39 | 39 |
|
40 | | -@Delete_cleanUp @vaccine_type_6IN1 @patient_id_Random @supplier_name_TPP |
41 | | -Scenario: Verify that the batch vaccination record will be successful updated by API request |
42 | | - Given batch file is created for below data as full dataset |
43 | | - | patient_id | unique_id | |
44 | | - | Random | Valid_NhsNumber | |
45 | | - When batch file is uploaded in s3 bucket |
46 | | - Then file will be moved to destination bucket and inf ack file will be created |
47 | | - And inf ack file has success status for processed batch file |
48 | | - And bus ack files will be created |
49 | | - And CSV bus ack will not have any entry of successfully processed records |
50 | | - And Json bus ack will only contain file metadata and no failure record entry |
51 | | - And Audit table will have correct status, queue name and record count for the processed batch file |
52 | | - And The imms event table will be populated with the correct data for 'created' event for records in batch file |
53 | | - And The delta table will be populated with the correct data for all created records in batch file |
54 | | - When Send a update for Immunization event created with vaccination detail being updated through API request |
55 | | - Then Api request will be successful and tables will be updated correctly |
| 40 | + @Delete_cleanUp @vaccine_type_6IN1 @patient_id_Random @supplier_name_TPP |
| 41 | + Scenario: Verify that the batch vaccination record will be successful updated by API request |
| 42 | + Given batch file is created for below data as full dataset |
| 43 | + | patient_id | unique_id | |
| 44 | + | Random | Valid_NhsNumber | |
| 45 | + When batch file is uploaded in s3 bucket |
| 46 | + Then file will be moved to destination bucket and inf ack file will be created |
| 47 | + And inf ack file has success status for processed batch file |
| 48 | + And bus ack files will be created |
| 49 | + And CSV bus ack will not have any entry of successfully processed records |
| 50 | + And Json bus ack will only contain file metadata and no failure record entry |
| 51 | + And Audit table will have correct status, queue name and record count for the processed batch file |
| 52 | + And The imms event table will be populated with the correct data for 'created' event for records in batch file |
| 53 | + And The delta table will be populated with the correct data for all created records in batch file |
| 54 | + When Send a update for Immunization event created with vaccination detail being updated through API request |
| 55 | + Then Api request will be successful and tables will be updated correctly |
56 | 56 |
|
57 | | -@Delete_cleanUp @vaccine_type_RSV @patient_id_Random @supplier_name_RAVS |
58 | | -Scenario: Verify that the API vaccination record will be successful updated and batch file will fail upload due to mandatory field missing |
59 | | - Given I have created a valid vaccination record through API |
60 | | - When Update to above vaccination record is made through batch file upload with mandatory field missing |
61 | | - And batch file is uploaded in s3 bucket |
62 | | - Then file will be moved to destination bucket and inf ack file will be created |
63 | | - And inf ack file has success status for processed batch file |
64 | | - And bus ack files will be created |
65 | | - And csv bus ack will have error records for all the updated records in the batch file |
66 | | - And json bus ack will have error records for all the updated records in the batch file |
67 | | - And The delta and imms event table will be populated with the correct data for api created event |
| 57 | + @Delete_cleanUp @vaccine_type_RSV @patient_id_Random @supplier_name_RAVS |
| 58 | + Scenario: Verify that the API vaccination record will be successful updated and batch file will fail upload due to mandatory field missing |
| 59 | + Given I have created a valid vaccination record through API |
| 60 | + When Update to above vaccination record is made through batch file upload with mandatory field missing |
| 61 | + And batch file is uploaded in s3 bucket |
| 62 | + Then file will be moved to destination bucket and inf ack file will be created |
| 63 | + And inf ack file has success status for processed batch file |
| 64 | + And bus ack files will be created |
| 65 | + And csv bus ack will have error records for all the updated records in the batch file |
| 66 | + And json bus ack will have error records for all the updated records in the batch file |
| 67 | + And The delta and imms event table will be populated with the correct data for api created event |
68 | 68 |
|
69 | | -@smoke |
70 | | -@Delete_cleanUp @vaccine_type_HIB @patient_id_Random @supplier_name_EMIS |
71 | | -Scenario: Verify that batch file record will ne unsuccessful if uses same or missing any unique identifier field |
72 | | - Given I have created a valid vaccination record through API, where unique_id and unique_id_uri will be same as batch file record |
73 | | - When batch file created for below data as full dataset and record has same or missing unique identifier for API record |
74 | | - And batch file is uploaded in s3 bucket |
75 | | - Then file will be moved to destination bucket and inf ack file will be created |
76 | | - And inf ack file has success status for processed batch file |
77 | | - And bus ack files will be created |
78 | | - And csv bus ack will have error records for all the updated records in the batch file |
79 | | - And json bus ack will have error records for all the updated records in the batch file |
80 | | - And The delta and imms event table will be populated with the correct data for api created event |
| 69 | + @smoke |
| 70 | + @Delete_cleanUp @vaccine_type_HIB @patient_id_Random @supplier_name_EMIS |
| 71 | + Scenario: Verify that batch file record will ne unsuccessful if uses same or missing any unique identifier field |
| 72 | + Given I have created a valid vaccination record through API, where unique_id and unique_id_uri will be same as batch file record |
| 73 | + When batch file created for below data as full dataset and record has same or missing unique identifier for API record |
| 74 | + And batch file is uploaded in s3 bucket |
| 75 | + Then file will be moved to destination bucket and inf ack file will be created |
| 76 | + And inf ack file has success status for processed batch file |
| 77 | + And bus ack files will be created |
| 78 | + And csv bus ack will have error records for all the updated records in the batch file |
| 79 | + And json bus ack will have error records for all the updated records in the batch file |
| 80 | + And The delta and imms event table will be populated with the correct data for api created event |
0 commit comments