-
Notifications
You must be signed in to change notification settings - Fork 4
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
Complete an integration test in the SIT environment #238
Comments
Integration Test (Prior Lakes)Tested in same manner as reaches on the following temporal ranges: 2024-08-25T01:00:00 to 2024-08-25T02:00:00:
2024-08-25T02:00:00 to 2024-08-25T05:00:00:
2024-08-25T05:00:00 to 2024-08-25T07:00:00:
Operations proceeded as expected. |
Integration Test (Nodes)Tested in same manner as reaches on the following temporal ranges: 2024-09-13T03:00:00 to 2024-09-13T09:00:00:
2024-09-13T10:00:00 to 2024-09-13T12:00:00:
2024-09-13T13:00:00 to 2024-09-13T23:59:59:
Operations proceeded as expected. |
Anomalies from SIT testing:
This revealed the need to test for a mismatch between collection shortname and Hydrocron SWOT and track ingest tables: #235 which also includes checking for Observed and Unassigned lakes. |
SIT test also revealed bug where the first query for granules in CMR was set to search in SIT and UAT by parent collection with a bearer token but the second query for granule files was not set up in the same way producing inconsistent results and sometimes not returning associated granule files. This led to the CNM function being invoked with an invalid CNM message. #248 |
SIT testing has concluded successfully. Results: https://cae-testrail.jpl.nasa.gov/testrail/index.php?/runs/view/48645&group_by=cases:title&group_order=asc |
To determine if the track ingest operations function to reconcile any granules that were not ingested into Hydrocron, a test should be performed in the services SIT environment. The test steps for SIT are documented here: https://wiki.jpl.nasa.gov/display/PD/Hydrocron#Hydrocron-SITtest(1.5.0)
The text was updated successfully, but these errors were encountered: