Skip to content
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

Create test script to detect data type mismatches between mapx and db table fields #995

Open
shawncrawley opened this issue Nov 22, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request Testing Relating to the QA/QC and testing of our processes
Milestone

Comments

@shawncrawley
Copy link
Collaborator

This idea was hatched from the troubleshooting on this VLab ticket. The comments there basically lay out the manual steps that could be automated to perform a sanity check across all services to ensure they are configured properly as per underlying field/column data types. This type of test script could be added as part of our QA/QC and CI/CD strategy, alongside apocalyptic testing.

@shawncrawley shawncrawley self-assigned this Nov 22, 2024
@shawncrawley shawncrawley added Testing Relating to the QA/QC and testing of our processes enhancement New feature or request labels Nov 22, 2024
@shawncrawley shawncrawley added this to the V2.1.x milestone Nov 22, 2024
shawncrawley added a commit that referenced this issue Dec 16, 2024
Refs #995 and #994
Adds a Jupyter Notebook script that compares the mapx files to the database tables they reference and updates the dtypes of the mapx accordingly. This commit also includes all of the mapx files that were updated on the initial execution of the script.
shawncrawley added a commit that referenced this issue Dec 16, 2024
shawncrawley added a commit that referenced this issue Dec 19, 2024
Refs #995 and #994
Adds a Jupyter Notebook script that compares the mapx files to the
database tables they reference and updates the dtypes of the mapx
accordingly. This commit also includes all of the mapx files that were
updated on the initial execution of the script.

It would be great to have this type of script be able to run
automatically as a CI/CD workflow whenever a PR is submitted. But for
now, I recommend that we add running this script to our deployment
checklist as another manual execution. The execution results in modified
mapx files, which should then be committed to a new branch, pushed, and
opened as a PR.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Testing Relating to the QA/QC and testing of our processes
Projects
None yet
Development

No branches or pull requests

1 participant