
Artos is a powerful, versatile, and user-friendly testing framework that helps test developers achieve their goals more efficiently and effectively.
- 01
Artos is released under MIT Open-Source license so license is granted free of charge
- 02
The Artos test framework is designed to be effortlessly runnable right out of the box without requiring any configuration changes. It comes with pre-configured and thoroughly tested utilities that enable engineers to focus on testing rather than setting up the framework.
Some examples of the utilities included in the framework are:
A pre-configured logging feature that can manage concurrent testing and create separate log files for each test thread.
A Pre-configured report generation that produces a variety of reports for internal or external use.
Built-in functionality for handling asserts, data conversion, data provider, image comparison, custom prompts creation, and more is included in the framework jar.
Overall, these pre-configured utilities make it easier for engineers to perform their testing tasks efficiently and effectively with the Artos framework.
- 03
The built-in UI test selector enhances visibility for test engineers and simplifies the debugging process by facilitating the re-run of failed test cases or the running of specific tests in a loop. This feature eliminates the need for users to modify production code for debugging purposes.
The Artos help test developers identify and reproduce failed test cases quickly and efficiently through features such as the “FAIL stamp”, “Known-to-fail test case management”, “Importance indicator” and “Failure indicator”.
Artos has the capability to automatically generate test scripts, which not only saves time for users but also minimizes the chances of errors.
Artos can print up to date test plan per test suite or for entire framework by executing few line of codes.
- 04
In many businesses, the test plan and test cases are managed separately in different systems, which can result in a disconnect and a lack of alignment between them. This can make it challenging to keep both in sync and up to date, leading to reduced confidence in the testing process.
The Artos framework addresses this issue by eliminating the disconnect between the test plan and test cases, and in some cases, eliminating the need for a separate test management system altogether. It encourages a feature-based structured test suite that can accommodate manual, semi-automated, and automated test cases within the same suite. With the Artos framework, users can write BDD or descriptive test plans directly within the test case, eliminating the need to refer to a separate document or management system during design or execution.
Furthermore, the Artos framework prints the test plan in a log file, making it easier to review and debug. If external review is necessary, the test plan can also be printed separately. All of these measures ensure that the test plan is always tightly bound to the test cases and remains up to date. Overall, the Artos framework helps to streamline the testing process and improve confidence in the quality of the tests being performed.
- 05
Artos provides a comprehensive and easily accessible solution for performing various types of testing, including unit, functional, and end-to-end testing. It can effectively manage diverse test cases within a single test suite, which can be organized by group or condition matching, such as manual, semi-automated, and automated.
Artos is a versatile testing tool that can be used to test a variety of products, including hardware, software, microservices, websites, mobile apps, standard and custom APIs, and even products without interfaces through visual regression testing.
Artos is written entirely in Java and is designed to be platform-independent. Artos test projects can be executed on any operating system that supports Java JVM, and it can be run on a headless build server or a PC or NUC-like system.
- 06
In addition to supporting traditional unit, functional, and end-to-end testing, the Artos testing framework also understands and can execute Cucumber feature files. This allows teams to benefit from the collaborative nature of BDD while still leveraging the power and flexibility of a comprehensive testing framework like Artos.
