SQL Calls in Service Suite

Recommended guidance

Details ofUse SQL filescalls in Service Suite only when tests need controlled database validation or setup. SQL calls must follow least privilege and usageshould canavoid bedestructive foundoperations unless they are explicitly approved and reversible.

What to define

• Database connection, schema, query, parameters, and timeout.
• Read-only versus write behavior and required permissions.
• Expected row count, values, or business validation criteria.
• Cleanup, rollback, and audit expectations for any data changes.

Best practices

1. Use test databases and controlled data whenever possible.
2. Never store passwords or production customer data in SQLunsecured Testing with Appvance.

   processSQLFile(String:file)

   Process aexamples.

3. Validate SQL file, results fromoutside the SQLmain queriessuite couldbefore beusing storedit in theautomated lockerruns.
4. Review usingquery theperformance calland storeInLockerlogs or the white board using the call storeInWhiteboard, processSQLFile can return one single row or a bunch of rows, for more information about processSQLFile see SQL Testing with Appvance.

   processSQLFile("{ds}/Test.sql");

   processSQLFile(String:file,JSONObject:entries)

   Process awhen SQL file,calls resultsaffect fromexecution the SQL queries could be stored in the locker using the call storeInLocker or the white board using the call storeInWhiteboard, processSQLFile can return one single row or a bunch of rows, for more information about processSQLFile see SQL Testing with Appvance.

   processSQLFile(String:file, Map<String, String>:entries)

   time.

Process a SQL file, results from the SQL queries could be stored in the locker using the call storeInLocker or the white board using the call storeInWhiteboard, processSQLFile can return one single row or a bunch of rows, for more information about processSQLFile see SQL Testing with Appvance.