-
Notifications
You must be signed in to change notification settings - Fork 2
CCM-13711: Test Data Letter Variations #324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
stevebux
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| # Change to the project directory | ||
| cd "$PROJECT_DIR" | ||
|
|
||
| # Define the three batches with different specification and group IDs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Define the four batches
| for batch in "${BATCHES[@]}"; do | ||
| # Parse specification-id and group-id from the batch definition | ||
| IFS=':' read -r SPEC_ID GROUP_ID <<< "$batch" | ||
| IFS=':' read -r SPEC_ID GROUP_ID TEST_LETTER BATCH_COUNT <<< "$batch" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and letter count in comment
|
checks are failing in the step "Run unit test suite" |
Description
Change the test PDFs and provide the ability to specify variations of test PDF for data generation
Update wrapper script to use different variations for each specification type
Add support for no PDF upload to generate missing PDF data cases (non-standard data set for on request)
Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.