documentation

Signed-off-by: Piotr PG Gajek <[email protected]>

Author: pgajek2

force-app/main/default/classes/main/standard-soql/SOQL.cls

@@ -2301,7 +2301,7 @@ public virtual inherited sharing class SOQL implements Queryable {
                 return this.sharingExecutor.toSObjects(this.builder.toString(), binder.getBindingMap(), this.accessMode);
             }
 
-            return Security.stripInaccessible(
+            return System.Security.stripInaccessible(
                 this.accessType,
                 this.sharingExecutor.toSObjects(this.builder.toString(), binder.getBindingMap(), this.accessMode)
             ).getRecords();
@@ -2324,7 +2324,7 @@ public virtual inherited sharing class SOQL implements Queryable {
 
         private void incrementQueryIssued() {
             // This counter is used only in unit tests to also track mocked queries.
-            if (!Test.isRunningTest() || System.isBatch() || System.isFuture() || System.isQueueable() || System.isScheduled()) {
+            if (!System.Test.isRunningTest() || System.isBatch() || System.isFuture() || System.isQueueable() || System.isScheduled()) {
                 return;
             }
 

website/docs/advanced-usage/mocking.md

@@ -99,6 +99,16 @@ Account `Description` and `Website` are null, even though they were specified. H
 **Note:**
 Currently, this field-stripping behavior applies only to simple fields (like `Name`, `Description`, etc.). Relationship fields and subqueries are not yet included in this logic — this may be addressed in future enhancements.
 
+### Queried Issued Count
+
+Mocked queries in SOQL Lib are counted towards the SOQL query limit, just like real queries. If the number of issued queries exceeds the limit, SOQL Lib will throw:
+
+```apex
+QueryException: Too many SOQL queries.
+```
+
+This behavior is consistent with Salesforce’s native limits, ensuring that your unit tests accurately reflect potential production scenarios.
+
 ## List of records
 
 ```apex