Orangebeard.io Reviews 1

Geschreven door het bedrijf

Orangebeard is a SaaS dashboard for accelerating automated testing in a CI / CD environment through Artificial Intelligence (Machine Learning). It’s is an integrated system that provides teams and organizations insight into all the tests they perform, to make the test automation process more efficient. Within Orangebeard it is possible to collect all test set results in one place. For example, Orangebeard provides an overview of all the different test types (such as unit, integration, system and chain tests). All test runs of all teams within an organization can be viewed at a glance. Orangebeard also provides insight into the test history and provides detailed test information per test. In addition, it is also visible per test set who has tested what, where, so that everyone within the team can view each other's results. Everything in real time. Orangebeard's system has the ability to learn from previous test results. Was an earlier test result due to a bug in the software, or did the test need to be adjusted? Orangebeard recognizes trends in failure reasons and will perform auto-analyzes, which will reduce the time required to manually analyze test results. This means that error analyzes take less time. In the “Control Room”, all test results from different projects are visualized in an extensive dashboard. In addition to the results of the performed test sets, trends are also made transparent. The test pyramid shows the distribution and coverage of test types. The dashboard is equipped with various visualisations to analyze the test results. This gives you, for example, insight into test (set) duration and failure rates. With the Auto Test Pilot (in development within the ITEA project) from Orangebeard the system learns to recognize which tests belong to which code. Orangebeard independently searches for the correlation between previously checked code and tests performed. With a code change, the system searches only for the tests that are relevant to this specific code change, so that the test time can be significantly reduced without compromising on quality requirements. So only what is needed is tested, resulting in a faster release.Toon meer