Troubleshooting & FAQ
Overview
This section lists common issues encountered during automation execution and how to resolve them.
Execution Issues
Scenario Not Executing
Symptoms - Scenario skipped - No execution logs
Checks
- enabled flag is set to true
- Environment matches execution configuration
- Platform and browser values are valid
Browser Not Launching
Symptoms - Execution stops immediately - Browser does not open
Checks - Browser is installed on the machine - Browser name is correctly configured - Headless mode settings are correct
Test Data Issues
Test Data Not Found
Symptoms - Variable resolution errors - Empty input fields
Checks
- Variable exists in test_data.json
- Variable name matches ${variable} usage
- File name is correctly linked in scenario.json
Locator Issues
Element Not Found
Symptoms - Step failure with element not found error
Checks - Locator type is correct - Locator value is valid - Application page is fully loaded - Timeout values are sufficient
Timeout & Performance Issues
Scenario Timeout
Symptoms - Scenario stops before completion
Checks - Increase scenario timeout - Check application performance - Reduce parallel execution count
Reporting Issues
Reports Not Generated
Symptoms - Execution completes - Reports folder is empty
Checks - Reporting flags are enabled - Write permissions exist - Execution completed successfully
General Best Practices
Start with smoke tests
Use sequential execution for debugging
Enable screenshots during failures
Validate configuration before execution
Avoid hardcoding environment-specific data
Frequently Asked Questions
Q: Can I run a single scenario?
A: Enable only the required scenario in scenario.json.
Q: Can I run without browser UI?
A: Enable headless=true in execution configuration.
Q: Where do I see execution results?
A: Under the reports/ directory.
Summary
Most execution issues are configuration-related. Always verify scenario, execution, and test data files before modifying framework behavior.