From 1364d801f7b25d556d12b3c159fa99c379bfaa25 Mon Sep 17 00:00:00 2001 From: andrew-platt Date: Thu, 15 Jan 2026 15:38:12 -0700 Subject: [PATCH] docs: Remove references to `pfunit` from docs (no longer used) --- docs/source/testing/index.rst | 13 ++++++------- docs/source/testing/unit_test.rst | 1 - 2 files changed, 6 insertions(+), 8 deletions(-) diff --git a/docs/source/testing/index.rst b/docs/source/testing/index.rst index 77fea3c218..cc91f40846 100644 --- a/docs/source/testing/index.rst +++ b/docs/source/testing/index.rst @@ -38,10 +38,9 @@ pushing new commits will trigger the tests. Obtaining and configuring the test suite ---------------------------------------- Portions of the test suite are linked to the OpenFAST repository through a -`git submodule`. Specifically, the following two repositories are included: +`git submodule`. Specifically, the following repository is included: - `r-test `__ -- `pFUnit `__ .. tip:: @@ -56,8 +55,8 @@ build process with an additional CMake flag: # BUILD_TESTING - Build the testing tree (Default: OFF) cmake .. -DBUILD_TESTING:BOOL=ON -Aside from this flag, the default CMake configuration is suitable for most systems. -See the :ref:`understanding_cmake` section for more details on configuring -the CMake targets. While the unit tests must be built with CMake due to its external -dependencies, the regression test may be executed without CMake, as described in -:ref:`python_driver`. +Aside from this flag, the default CMake configuration is suitable for most +systems. See the :ref:`understanding_cmake` section for more details on +configuring the CMake targets. While the unit tests must be built with CMake due +to its dependency on `test_drive` (included in the source code), the regression +test may be executed without CMake, as described in :ref:`python_driver`. diff --git a/docs/source/testing/unit_test.rst b/docs/source/testing/unit_test.rst index 0b3cb15a0a..8e421df93d 100644 --- a/docs/source/testing/unit_test.rst +++ b/docs/source/testing/unit_test.rst @@ -113,4 +113,3 @@ Some useful topics to consider when developing and testing for OpenFAST are: - `Test driven development `__ - `Separation of concerns `__ -- `pFUnit usage `__