Skip to content

Demo

Demo application: https://demo.elbase.io

The demo application is a modified version of the main application

Differences from the main application:

  1. User registration is disabled
  2. Sign in is not required
  3. The application has publicly available pre-filled data to demonstrate the product capabilities

Demo 1

For this demo, the following GitHub repositories were tested:

  1. FastAPI tests (the tests use pytest)
  2. Next.js unit tests (the tests use Jest)
  3. Mongoose tests (the tests use Mocha)

The demo walk-through:

  1. Open https://demo.elbase.io
  2. In the "Query" section, enter the following and click the "Run query" button 
    #example = "github" group_by(#repo)
    The query returned results that have "example" label with "github" value, and grouped the results by the value of the "repo" label.
  3. In the "Groups" section, there are three groups, one for each of the "repo" label value (FastAPI tests, Next.js tests and Mongoose tests).
    For each group there is an aggregated status, as well as an aggregated status for all the groups (in the top right corner of the "Groups" section).
  4. Select any of the groups.
  5. In the "Testcases" section, there are test cases that belong to the selected group.
    For each test case there is a status, as well as an aggregated status for the test cases (in the top right corner of the "Testcases" section).
  6. Select any of the test cases.
  7. In the "Details" section on the right side of the application, there are details of the selected test case.
  8. In the "Details" section, switch to the "Session details" tab to view the test sessions properties and labels.

Demo 2: Test Failures

Demo 2

This demo shows how test failures are show on UI.

The demo walk-through:

  1. Open https://demo.elbase.io
  2. In the "Query" section, enter the following and click the "Run query" button 
    #example = "reporting"
    The query returned results that have "example" label with "reporting" value.
  3. In the "Testcases" section, there are test cases that belong to a session that has the label.
    For each test case there is a status, as well as an aggregated status for the test cases (in the top right corner of the "Testcases" section).
  4. Select a failed test case, for instance the second one (named "test_1_err").
  5. In the "Details" section on the right side of the application, there are details of the selected test case.
    Check the "Output" section at the bottom of the "Details" section for the error.

Demo 3: Grouping

Demo 3

This demo shows how test to group test results and use the groups to navigate the test results.

The demo walk-through:

  1. Open https://demo.elbase.io
  2. In the "Query" section, enter the following and click the "Run query" button 
    #example = "grouping" group_by(#version, #target)
    The query returned results that have "example" label with "grouping" value.
    The results are grouped by the values of "version" x "target" labels.
  3. In the "Groups" section, there are groups for each of the "version" x "target" label values.
    It is easy to what group have failures.
  4. Modify query to get only results for version 0.0.1-rc.2: 
    #example = "grouping" and #version = "0.0.1-rc.2" group_by(#target)
    The returned results are grouped by target, and it is clear where test failed.