-
Notifications
You must be signed in to change notification settings - Fork 68
[AL-5942] Exports v2 integration tests #1187
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
Conversation
1749dc8 to
58e277e
Compare
328f4d8 to
d985579
Compare
| import pytest | ||
|
|
||
|
|
||
| @pytest.mark.parametrize('data_rows', [5], indirect=True) |
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.
Why does this have to be 5 data rows? Can we reduce to 2?
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.
We can. Does it impact the the test run time by a large extent? (curious)
I am dropping it to 2 anyway.
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.
well as I am working right now to optimize fixtures, it looks like the biggest bottleneck is creation of data rows, because this has to go to es and come back
I can not say that 2 vs 5 will make a world of difference, but generally I think we never need more than 2 data rows in our integration tests to represent the concept of 'many'.
| ]) == set(data_row_ids) | ||
|
|
||
|
|
||
| @pytest.mark.parametrize('data_rows', [5], indirect=True) |
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.
Same, why 5?
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.
changed it to 3. This test needs a min of 3 datarows.
https://labelbox.atlassian.net/browse/AL-5942
tests/integration/annotation_import/test_data_types.py::test_import_data_types_v2 still has the exports v2 tests for all the datatypes. This test cases does testing for both import and export pipelines. So I let it be here for now. Although it is ideal to have a similar test case in the exports suite. But in view of not duplicating the test cases (which increases the run time), i let it be here. This is the only exports v2 related test case that is not inside the exports_v2 suite.