What makes DASKALOS TestRunner Different?

DASKALOS TestRunner is designed to streamline test automation, reduce development bottlenecks, and enable seamless collaboration between automation developers, subject matter experts (SMEs), and test engineers. Unlike traditional test automation frameworks, DASKALOS is structured into three core components, ensuring scalability, flexibility, and cost-effectiveness.

A Modular Approach to Test Automation

DASKALOS TestRunner is broken into three distinct components:

  1. Automation Code (Java, WebDriver, Selenium)
  2. Configuarion
  3. Object Repositories
  4. Test Cases

Automation Code: Java, WebDriver, and Selenium

At its core, DASKALOS is built using Java, Selenium WebDriver, and industry-standard automation practices. The automation engine is designed with extensibility in mind, using a plugin architecture that allows custom functionality to be easily integrated.

  • Encapsulates Core Selenium Functions – The automation code wraps essential WebDriver operations, ensuring consistent and reusable interactions.
  • Flexible and Scalable – Built with standard Java design principles, allowing developers to extend or modify test execution behavior.
  • No Special Tools or Integrations Required – Runs from the command line, requiring only Java and Selenium runtimes, making it easy to integrate into existing CI/CD pipelines.

By keeping the automation code separate, developers can focus on building robust automation libraries while non-developers handle test case creation independently.

Seamless Configuration for Multi-Environment Deployment

As part of its modular design, DASKALOS TestRunner uses configuration files to manage test execution settings, making it easy to deploy and run tests across different environments. Instead of hardcoding environment-specific details, all critical configurations—such as browser settings, test execution modes, and external integrations—are stored in separate properties files. This approach allows teams to:

  • Easily switch between environments (e.g., Dev, QA, Staging, Production) without modifying test scripts.
  • Maintain consistent test execution across different setups, reducing manual configuration errors.
  • Scale test automation to support multiple application versions with minimal effort.

By keeping configuration independent from test cases and automation logic, DASKALOS ensures adaptability, efficiency, and streamlined deployment across various testing environments.

Object Repository: Centralized and Maintainable

The Object Repository is stored separately from the test cases and the automation code. This means test elements can be modified, updated, or extended without requiring changes to test scripts or automation logic.

  • Uses Standard Java Properties Format – Object locators are stored in a structured, readable format using dot notation.
  • Supports Dynamic Placeholders – Object locators can include curly brace { } placeholders, allowing dynamic values to be inserted at runtime.
  • Shared Control – Automation engineers, testers, and SMEs can collaborate on object repository updates without modifying automation code.
  • Eliminates Bottlenecks – Since object repositories are independent, changes to web elements (such as updates to XPath or CSS selectors) do not require code recompilation, minimizing disruptions to test execution.

Test Cases: SME-Friendly and Easily Maintained

DASKALOS TestRunner uses a keyword-driven test format, making test case creation accessible to both automation engineers and SMEs.

  • Structured as CSV Files – Test cases are stored in a simple, human-readable CSV format that requires no programming knowledge.
  • No Code Compilation Required – Tests can be updated, modified, or added without rebuilding the automation framework.
  • Reusability and Modularity – Common test steps can be modularized and reused across different test cases, reducing redundancy.
  • Supports Parameterized Data – Test cases can include placeholders ([ ]) for dynamic data substitution, allowing the same test to run with multiple data sets.

By giving SMEs the ability to write test cases without technical expertise, test creation is no longer a bottleneck, and automation teams can scale efficiently.

Key Benefits of DASKALOS TestRunner

Eliminates Bottlenecks and Enhances Collaboration

By separating automation code, object repositories, and test cases, different team members can work in parallel. This removes traditional test automation bottlenecks, ensuring that:

  • Automation engineers focus on framework development.
  • SMEs and manual testers create and manage test cases.
  • Repository updates do not impact automation scripts.

Reduces the Overall Size of the Automation Team

With traditional test automation frameworks, test creation often requires programming skills, leading to larger automation teams. DASKALOS eliminates this dependency by allowing non-technical users to create and manage tests, reducing the need for specialized automation engineers.

No Code Recompilation for Test or Repository Changes

Because test cases and object repositories are separate from the automation code, updates do not require code recompilation or redeployment. This means:

  • Faster test iterations
  • Lower maintenance costs
  • More agile test execution

Seamless Command-Line Execution for CI/CD Integration

DASKALOS runs directly from the command line, making it easy to integrate with existing CI/CD systems. No additional tools or complex configurations are needed—simply run the tests as part of any automation pipeline.

Why Choose DASKALOS TestRunner?

DASKALOS TestRunner is not just another automation tool—it’s an optimized, cost-effective, and scalable solution designed for modern test automation teams. By focusing on flexibility, ease of use, and efficient collaboration, it significantly reduces test maintenance overhead while maximizing efficiency.

Ready to experience faster test automation with less complexity? DASKALOS TestRunner makes it happen.