This is an automated email from the ASF dual-hosted git repository.

gurwls223 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark.git


The following commit(s) were added to refs/heads/master by this push:
     new 2fd1f10a164 [SPARK-45729][PYTHON][DOCS] Fix PySpark testing guide links
2fd1f10a164 is described below

commit 2fd1f10a16427fc03dc92b3a3d0308d214bb0015
Author: Amanda Liu <[email protected]>
AuthorDate: Tue Oct 31 12:37:18 2023 +0900

    [SPARK-45729][PYTHON][DOCS] Fix PySpark testing guide links
    
    ### What changes were proposed in this pull request?
    This PR fixes links in the PySpark testing guidelines page (hyperlinks 
words instead of displaying the URLs).
    
    ### Why are the changes needed?
    The official PySpark testing guidelines page is the highest-ranking Google 
Search result for PySpark testing. These changes clean up the guide and improve 
the user experience.
    
    ### Does this PR introduce _any_ user-facing change?
    Yes, the changes affect the user-facing testing guidelines page.
    
    ### How was this patch tested?
    Existing tests
    
    ### Was this patch authored or co-authored using generative AI tooling?
    No
    
    Closes #43587 from asl3/fix-testing-docs-links.
    
    Authored-by: Amanda Liu <[email protected]>
    Signed-off-by: Hyukjin Kwon <[email protected]>
---
 python/docs/source/getting_started/testing_pyspark.ipynb | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/python/docs/source/getting_started/testing_pyspark.ipynb 
b/python/docs/source/getting_started/testing_pyspark.ipynb
index 268ace04376..afccbe4004c 100644
--- a/python/docs/source/getting_started/testing_pyspark.ipynb
+++ b/python/docs/source/getting_started/testing_pyspark.ipynb
@@ -9,7 +9,7 @@
     "\n",
     "This guide is a reference for writing robust tests for PySpark code.\n",
     "\n",
-    "To view the docs for PySpark test utils, see here. To see the code for 
PySpark built-in test utils, check out the Spark repository here. To see the 
JIRA board tickets for the PySpark test framework, see here."
+    "To view the docs for PySpark test utils, see 
[here](https://spark.apache.org/docs/latest/api/python/reference/pyspark.testing.html)."
    ]
   },
   {
@@ -190,10 +190,10 @@
    "id": "c67be105-f6b1-4083-ad11-9e819331eae8",
    "metadata": {},
    "source": [
-    "### Option 2: Using [Unit 
Test](https://docs.python.org/3/library/unittest.html)\n",
+    "### Option 2: Using Unit Test\n",
     "For more complex testing scenarios, you may want to use a testing 
framework.\n",
     "\n",
-    "One of the most popular testing framework options is unit tests. Let’s 
walk through how you can use the built-in Python `unittest` library to write 
PySpark tests. For more information about the `unittest` library, see here: 
https://docs.python.org/3/library/unittest.html.  \n",
+    "One of the most popular testing framework options is unit tests. Let’s 
walk through how you can use the built-in Python `unittest` library to write 
PySpark tests. \n",
     "\n",
     "First, you will need a Spark session. You can use the `@classmethod` 
decorator from the `unittest` package to take care of setting up and tearing 
down a Spark session."
    ]
@@ -271,9 +271,9 @@
    "id": "7d79e53d-cc1e-4fdf-a069-478337bed83d",
    "metadata": {},
    "source": [
-    "### Option 3: Using 
[Pytest](https://docs.pytest.org/en/7.1.x/contents.html)\n",
+    "### Option 3: Using Pytest\n",
     "\n",
-    "We can also write our tests with `pytest`, which is one of the most 
popular Python testing frameworks. For more information about `pytest`, see the 
docs here: https://docs.pytest.org/en/7.1.x/contents.html.\n";,
+    "We can also write our tests with `pytest`, which is one of the most 
popular Python testing frameworks.\n",
     "\n",
     "Using a `pytest` fixture allows us to share a spark session across tests, 
tearing it down when the tests are complete."
    ]


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

Reply via email to