-
Notifications
You must be signed in to change notification settings - Fork 61
Add Bulk validations test #1708
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: mvp_demo
Are you sure you want to change the base?
Conversation
Signed-off-by: Saad Khan <[email protected]>
|
|
||
|
|
||
| @pytest.mark.test_bulk_api_ros | ||
| @pytest.mark.parametrize("start, end, expected_error", [ |
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.
@khansaad Can you update the test documentation with the test scenarios. Also add a description in the PR.
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.
Done
Signed-off-by: Saad Khan <[email protected]>
Signed-off-by: Saad Khan <[email protected]>
…s-test # Conflicts: # tests/scripts/helpers/utils.py
|
bulk-test-results.zip |
| validate_job_status(response.json()["job_id"], URL, caplog) | ||
|
|
||
|
|
||
| @pytest.mark.test_bulk_api_ros |
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.
Is this marker added in the tests list in the script to run? If not, you can add negative/sanity marker too.
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.
Yes, its added in the pytest.ini file
chandrams
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
| ("2024-01-01 10:00:00", "2024-01-01T12:00:00Z", "Invalid date format. Must follow ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ) for the jobId:"), # bad format | ||
| ("2025-01-02T12:00:00Z", "2025-01-01T12:00:00Z", "Start time should be before end time for the jobId:"), # start > end | ||
| # less than 24 hours difference | ||
| ("2025-01-01T00:00:00Z", "2025-01-01T10:00:00Z", "Time range must be between 24 hours and 15 days for the jobId:"), |
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.
@khansaad I don't think we should have this time range check, please verify and update
chandrams
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.
@khansaad I don't think we should have this time range check, please verify and update the code & tests
Description
This PR contains tests for the validations added as part of PR #1557
Fixes # (issue)
Type of change
How has this been tested?
Please describe the tests that were run to verify your changes and steps to reproduce. Please specify any test configuration required.
Test Configuration
Checklist 🎯
Additional information
Include any additional information such as links, test results, screenshots here