docs: adds details to test results processor config option

docs/Configuration.md

@@ -1262,6 +1262,8 @@ This option allows the use of a custom results processor. This processor must be
 }
 ```
 
+`testResultsProcessor` and `reporters` are very similar to each other. One difference is that a test result processor only gets called after all tests finished. Whereas a reporter has the ability to receive test results after individual tests and/or test suites are finished.
+
 ### `testRunner` \[string]
 
 Default: `jest-circus/runner`

website/versioned_docs/version-25.x/Configuration.md

@@ -1108,6 +1108,8 @@ This option allows the use of a custom results processor. This processor must be
 }
 ```
 
+`testResultsProcessor` and `reporters` are very similar to each other. One difference is that a test result processor only gets called after all tests finished. Whereas a reporter has the ability to receive test results after individual tests and/or test suites are finished.
+
 ### `testRunner` \[string]
 
 Default: `jasmine2`

website/versioned_docs/version-26.x/Configuration.md

@@ -1194,6 +1194,8 @@ This option allows the use of a custom results processor. This processor must be
 }
 ```
 
+`testResultsProcessor` and `reporters` are very similar to each other. One difference is that a test result processor only gets called after all tests finished. Whereas a reporter has the ability to receive test results after individual tests and/or test suites are finished.
+
 ### `testRunner` \[string]
 
 Default: `jasmine2`

website/versioned_docs/version-27.0/Configuration.md

@@ -1221,6 +1221,8 @@ This option allows the use of a custom results processor. This processor must be
 }
 ```
 
+`testResultsProcessor` and `reporters` are very similar to each other. One difference is that a test result processor only gets called after all tests finished. Whereas a reporter has the ability to receive test results after individual tests and/or test suites are finished.
+
 ### `testRunner` \[string]
 
 Default: `jest-circus/runner`

website/versioned_docs/version-27.1/Configuration.md

@@ -1256,6 +1256,8 @@ This option allows the use of a custom results processor. This processor must be
 }
 ```
 
+`testResultsProcessor` and `reporters` are very similar to each other. One difference is that a test result processor only gets called after all tests finished. Whereas a reporter has the ability to receive test results after individual tests and/or test suites are finished.
+
 ### `testRunner` \[string]
 
 Default: `jest-circus/runner`

website/versioned_docs/version-27.2/Configuration.md

@@ -1260,6 +1260,8 @@ This option allows the use of a custom results processor. This processor must be
 }
 ```
 
+`testResultsProcessor` and `reporters` are very similar to each other. One difference is that a test result processor only gets called after all tests finished. Whereas a reporter has the ability to receive test results after individual tests and/or test suites are finished.
+
 ### `testRunner` \[string]
 
 Default: `jest-circus/runner`

website/versioned_docs/version-27.4/Configuration.md

@@ -1262,6 +1262,8 @@ This option allows the use of a custom results processor. This processor must be
 }
 ```
 
+`testResultsProcessor` and `reporters` are very similar to each other. One difference is that a test result processor only gets called after all tests finished. Whereas a reporter has the ability to receive test results after individual tests and/or test suites are finished.
+
 ### `testRunner` \[string]
 
 Default: `jest-circus/runner`

website/versioned_docs/version-27.5/Configuration.md

@@ -1262,6 +1262,8 @@ This option allows the use of a custom results processor. This processor must be
 }
 ```
 
+`testResultsProcessor` and `reporters` are very similar to each other. One difference is that a test result processor only gets called after all tests finished. Whereas a reporter has the ability to receive test results after individual tests and/or test suites are finished.
+
 ### `testRunner` \[string]
 
 Default: `jest-circus/runner`