zhengruifeng opened a new pull request, #55618:
URL: https://github.com/apache/spark/pull/55618

   ### What changes were proposed in this pull request?
   
   The Connect parity test file 
`python/pyspark/sql/tests/connect/test_resources.py` and its class 
`ResourceProfileTests` are the only ones in `python/pyspark/sql/tests/connect/` 
that don't follow the naming convention used by 200+ other parity tests:
   
   - Filename should be `test_parity_<name>.py`.
   - Class name should be `<Name>ParityTests`.
   
   This PR renames:
   - `python/pyspark/sql/tests/connect/test_resources.py` -> 
`python/pyspark/sql/tests/connect/test_parity_resources.py`
   - `ResourceProfileTests` -> `ResourceProfileParityTests`
   
   References to the old module path are updated in 
`dev/sparktestsupport/modules.py` and 
`.github/workflows/build_python_connect.yml`.
   
   ### Why are the changes needed?
   
   Consistency. The `test_parity_*` filename and `*ParityTests` class name are 
the established convention across the Connect parity test suite; this rename 
brings the resource profile parity tests in line and makes it easier to locate 
and identify parity tests at a glance.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No. Test-only change with no behavioral impact.
   
   ### How was this patch tested?
   
   Existing tests; only filename and class name changed. The test module is 
still discovered through `dev/sparktestsupport/modules.py` and the connect CI 
workflow.
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   Generated-by: Claude Code (Opus 4.7)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to