[
https://issues.apache.org/jira/browse/ARROW-17016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605771#comment-17605771
]
Alenka Frim commented on ARROW-17016:
-------------------------------------
In that case there will have to be extra environment variable specified by the
developer/user before building PyArrow to turn the tests on for PyArrow
separately. I am fine with this approach and can go with that.
There was also a question Raul had on this approach when we brainstormed and I
wonder also: will we have to, in this case, have similar third party dependency
infrastructure as we do for Arrow C++ to download third party dependencies? Or
will that not be needed only for GTest?
> [C++][Python] Run Arrow Python C++ with pytest and make sure they are run by
> the CI
> -----------------------------------------------------------------------------------
>
> Key: ARROW-17016
> URL: https://issues.apache.org/jira/browse/ARROW-17016
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: C++, Python
> Reporter: Alenka Frim
> Assignee: Alenka Frim
> Priority: Major
> Labels: pull-request-available
> Fix For: 10.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After [https://github.com/apache/arrow/pull/13311] is merged{-}, the tests
> for C PyArrow should be moved to Cython and the documentation about running
> the tests with GTest should be removed.{-} we should:
> - try to run the tests from the pytest to make the whole process of code
> quality check simplified.
> - make sure the CI runs these PyArrow C++ test. Currently they are not being
> run on the CI due to all the builds having GTest not bundled, see:
> [https://arrow.apache.org/docs/dev/developers/python.html#testing-pyarrow-c]
> The migration of the tests to Cython has not proved as a good option as
> there are couple of tests that should stay in the C++, for example
> [TestMoves|https://github.com/apache/arrow/blob/master/python/pyarrow/src/python_test.cc#L48-L62]
> and similar. For this reason we will find some other solution to keep using
> GTest and run them with pytest, if possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
