Testlum Configuration

To get started with Testlum, you need to configure your testing environment properly. Testlum supports a modular configuration approach using XML files, allowing flexibility and ease of setup across different environments and integration points.

Testlum Structure

To start working with Testlum, you need to create a directory with your project's resources which will contain the main folders of your directory and global-config.xml file with global configuration settings for your project.

Detailed guide and explanation how to do this you can find right here.

Global Configuration

The main entry point for your setup is the global-config.xml file. This file contains top-level settings that control the entire framework's behavior, including:

• Defined environments (e.g., dev, qa, prod)
• Global parameters
• Scenario execution options (e.g., stopScenarioOnFailure)
• Parallel execution and component control

📁 Location: test-resources-base-folder/global-config.xml

Detailed guide for global configuration setup can be found here.

📁 Example folder structure:

config/
├── qa/
│   ├── ui.xml
│   └── integration.xml
├── prod/
│   ├── ui.xml
│   └── integration.xml

For each environment you define (e.g., qa, prod, staging), you should have a separate folder in the config directory. Each folder should include the following configurations:

UI Configuration

The main place where you can set configurations for the WEB, Native, and Mobile Browser tests.

📁 Location: test-resources-base-folder/config/env-folder/ui.xml

Defines UI-specific settings such as:

• Browser type (Chrome, Firefox, etc.)
• Browser options
• Timeout settings
• Screenshots recording during execution
• Mobile Browser testing сonfiguration
• Native mobile applications configuration

Detailed guide for ui configuration setup can be found here.

Integrations Configuration

The main place where you can set configurations for the list of supported integrations.

📁 Location: test-resources-base-folder/config/env-folder/integration.xml

Defines settings for testing supported services such as:

• Databases
• Messaging
• Queues
• AWS
• API
• WebSockets

Detailed guide for integrations configuration setup can be found here.

✅ Best Practices

• Use consistent naming for environment folders.
• Keep sensitive data out of version control. Use placeholders or environment variables where possible.
• Validate your XML files before running scenarios to avoid silent config errors.