Testing and debugging applications
-
- UpdatedAug 3, 2023
- 1 minute read
- Vancouver
- Building applications
The Vancouver release is no longer supported. As such, the product documentation and release notes are provided for informational purposes only, and will not be updated.
Verify the application meets your business requirements. Your testing should cover record operations (such as create, read, update, and delete), user interface elements (such as views and UI policies), runtime operations (such as business rules), and event script actions.
Testing and debugging on Core UI
- Automated Test Framework
- Create and run automated tests to confirm that your instance works after making a change. Review failed test results to identify the changes that caused the failure and the changes that you should review.
- Debugging scripts
- Debug scripts using session logs and Now Platform debugging tools, such as a walk-through script debugger and error messages that display in the UI.
- Script Debugger and Session Log
- The Script Debugger enables users with the script_debugger role to debug server-side JavaScript, while the Session Log enables you to view and download required logs.
- Script Tracer and debugging scripts
- Use the Script Tracer to filter your debugging search and quickly narrow down script problems. Finding specific lines of scripts, rather than doing a wide search, helps save time and improves productivity.