Using the Log Views

Functionize provides powerful logging and history features that help teams track changes, troubleshoot issues, and restore tests when needed. Together, these tools offer transparency, accountability, and actionable insights into both test case evolution and execution behavior.

Audit Logs

The Audit Log tracks the complete history of changes made to each test and page object. It shows who made changes, when they occurred, and what was updated. This ensures full visibility into the lifecycle of your test assets and helps maintain compliance or audit requirements.

Key Capabilities

• View change history for every test or page object.
• Identify who made edits and when.
• Filter activities by date, editor, or action type.
• Restore tests to earlier versions or create new test cases from prior iterations.
• Export logs as CSV for reporting or review.

Audit Log Filters

1. Open Test Detail Page – open a test to the Test Detail view.
2. Access Audit Log – click the Settings menu → Audit Log.
3. Apply Date Filter – filter changes within a specific start/end date.
4. Select Editor – filter by a specific user.
5. Select Action Type – filter by action category (e.g., Test Run, Delete Action, Title Change, Add Action, etc.).
6. Export CSV – download the filtered log data for offline use.

Note: Not all entries can be restored. For example, execution events (Live Execution, Headless Run, etc.) are not restorable. These appear only if the Group By filter is set to Test Run.

Restoring a Test Case

Use this option to revert a test back to a previous version.

1. Open the test’s Detail Page.
2. Go to Settings → Audit Log.
3. Select the version you want to restore.
4. Click Restore.
5. Confirm restoration.
6. Refresh the Audit Log to see the update.

Note: Once restored, the test settings and change history will also be reverted to the restored version.

Restoring to a New Test Case

Use this when you want to revert to an earlier version without losing the current version.

1. Open the test’s Detail Page.
2. Access the Audit Log.
3. Select the version to restore.
4. Check Restore to new test case.
5. Enter a new test case name.
6. Click Restore.
7. Confirm the restoration.
8. View the new case from the Test Case Listing Page.

Previewing a Reverted Test Case

Before restoring, you can preview the version:

1. Open the test or page object.
2. Access the Audit Log.
3. Select a version.
4. Click Preview.
5. Review the actions, settings, and screenshots (via Slider View).

Note: Preview is read-only—you cannot edit actions from this view.

Restoring from Preview

From the Preview page:

• Click Restore to revert directly.
• Or select Restore to new test case, provide a new name, and confirm.

Console Logs

The Console Logs capture JavaScript errors, warnings, and console outputs relevant to your test executions. They help you identify client-side issues like blocked resources or CORS problems.

Benefits

• Targeted Troubleshooting – filters out irrelevant console noise.
• Contextual Errors – links logs directly to the test step where they occurred.
• Actionable Insights – provides clear next steps (e.g., fix syntax, update CORS headers, adjust API calls).

Accessing Console Logs

1. Navigate to the Test Details page of a completed execution.
2. Click View Result (or the View button next to an action).
3. Select the Console tab.

Common Console Errors

Network Logs

The Network Logs capture and filter network requests, responses, and HTTP status codes during test runs. They help identify timeouts, failed requests, or DNS issues, especially useful when testing applications behind firewalls.

Benefits

• Targeted Troubleshooting – reduces noise, focusing only on relevant failures.
• Contextual Errors – ties logs directly to the test step.
• Actionable Insights – helps address server, DNS, or firewall issues quickly.

Accessing Network Logs

1. Go to the Test Details page for a completed run.
2. Click View Result (or the View button for any action).
3. Select the Network tab.

Common Network Errors

Summary

• Audit Logs → Track change history and restore test cases.
• Console Logs → Debug JavaScript and client-side errors.
• Network Logs → Troubleshoot HTTP and server/network issues.

Together, these features give you end-to-end visibility into both test changes and runtime issues—helping ensure stability, accountability, and reliability in your automated testing.