DASKALOS TestRunner if an automation framework and tool set. Unlike most of the current automation frameworks, they require time to learn and understand before building your first automated tests. This can take days to several weeks. That does not take into account the time required to determine best practices that work for your environment and testing strategies.
With all the different options out there, why would I take the time and effort to create a new framework and tool set? Especially one that takes a unique approach to what a lot of experts have been promoting. When I started in my career in software development almost thirty years ago, there was a simple term we used, Keep It Super Simple. This is a philosophy I have always tried to adhere to with every project I have worked on.
Over the past few years I have seen several frameworks and tool implementations, and one thing I see in common is they are over engineered. They make use of the latest programming techniques just because they are new and don’t add any real additional functionality to the automation framework. Sometimes they add more complexity, increased maintenance. In following the Keep It Super Simple practice of software development, these new features, although they can provide some extra features, the cost is too high. That does not mean this is not suitable for some situations, but it is not suitable for every situation and every company.
After working with several companies, with large and small quality assurance teams, those with new products and those with legacy applications that have been in production for years. The two big issues I have seen with the automation frameworks and tools is there is no real good middle ground. The frameworks provide the most flexibility to handle just about any situation, however; they require highly skilled engineers that understand testing concepts and software design. In most cases, this will require expanding the quality assurance team to include these developers. These frameworks also exclude the team members with the most experience of testing the applications because of how the design of the framework. Some tools marketed as quick and easy to use, have a lot of limitations. If expandable, it will require experienced developers to make the required changes.
For these reasons, I created DASKALOS TestRunner. I wanted a framework and toolset ready to use ‘out-of-the-box’; easy to use without sacrificing features; eliminate the weeks or months needed to adopt other frameworks; and maximize the return on investment. These frameworks also require the automation developer to be an expert in multiple areas including software development, automation testing, creating object locators, building automation tests.
DASKALOS TestRunner separates the automation framework from the other components required for running an automated test. This separation of responsibilities removes some work off the developer and allows the subject mater experts to take an active role in creating automated tests. I will cover the details in future posts. In short, DASKALOS TestRunner uses multiple automation methodologies combining the best features of them. The automation test steps follow the keyword driven methodology making the test creation easy.