Qase Docs
Help CenterAPI DocsRoadmapSign up for free
  • General
    • Qase docs
    • Get started with the Qase platform
      • Account settings
      • Projects
      • Test suites
      • Test cases
        • Test Case Parameters
        • Test case review
        • Shared steps
        • Import test cases
        • Export test cases
        • Trash bin
        • Muted Tests
        • System fields
        • Nested steps
        • Test case actions
        • Filters
      • Requirements Traceability Report
      • AI Test Case Generator
    • Execute testing
      • Test plan
      • Test runs
      • Configurations
      • Environments
    • Issues tracking
      • Defects
      • Milestones
      • Requirements
    • Analytics
      • Dashboards
      • Queries (QQL, Qase Query Language)
      • Saved queries
    • Webhooks
      • Test Case
      • Test suite
      • Test plan
      • Shared step
      • Milestone
      • Custom field
      • Test run
      • Defect
      • Test review
  • AIDEN
    • AIDEN - QA Architect
  • Guide: Action editor
  • Administration
    • Workspace management
      • Users
      • Invites
      • Groups
      • Roles
      • Fields
      • Custom fields
      • Notifications
      • Tags
      • Attachments
      • Audit logs
      • Hotkeys
    • SSO / SAML instructions
      • AzureAD
      • OneLogin
      • Google Workspace
      • Okta
      • JumpCloud
    • SCIM
      • User lifecycle management with SCIM
      • Enable SCIM
      • Users
      • Discovery features
      • Errors
    • Security
      • SOC 2 Type II / SOC 3
      • ISO/IEC 27001:2022
      • Penetration testing report
      • Subprocessors
      • Qase IP addresses
    • Billing
      • Billing options
    • Subscriptions
      • Free plan
      • Startup plan
      • Business plan
      • Enterprise plan
  • Apps
    • Issue tracking
      • Jira Cloud
      • Jira Server/Datacenter Plugin installation
      • GitHub
      • Asana
      • Linear
      • Monday
      • ClickUp
      • Trello
      • Azure DevOps
      • GitLab
      • YouTrack
      • Redmine
    • CI/CD
      • Jenkins
      • BitBucket
      • GitHub CI
      • GitLab CI
    • Chats
      • Slack
  • Automation
    • Qase API
    • Reporters
      • JavaScript
        • Playwright
        • Cypress
        • Mocha
        • Newman
        • Jest
        • WebDriverIO
        • CucumberJS
        • TestCafe
      • Python
        • Pytest
        • Robot Framework
        • Behave
        • Tavern
      • Java
        • TestNG
        • JUnit 4
        • JUnit 5
        • Cucumber 3 (jvm)
        • Cucumber 4 (jvm)
        • Cucumber 5 (jvm)
        • Cucumber 6 (jvm)
        • Cucumber 7 (jvm)
      • PHP
        • PHPUnit
        • Codeception
      • Kotlin
        • Kaspresso
    • Qase CLI App
      • XCTest
Powered by GitBook
On this page
  • Repository Analyser
  • Let's start automating!
  • Adding the environment
  • Authorization
  • Generation
  • Executing the automated tests
  1. AIDEN

AIDEN - QA Architect

PreviousTest reviewNextGuide: Action editor

Last updated 26 days ago

While Manual testing has been the cornerstone of software quality for decades, it is slow, costly, and error-prone. And, traditional test automation requires deep technical expertise, extensive infrastructure, and ongoing maintenance — and these are barriers that prevent many teams from adopting it effectively.

AIDEN eliminates these challenges by allowing users to create, execute, and maintain automated tests using natural language instead of working with code.

By leveraging Generative AI, AIDEN transforms test descriptions into executable test scripts in Qase Cloud, runs them in parallel across multiple browsers.

With AIDEN, you can analyse your repository, generate automated test code from your manual test cases, and execute the tests in Qase Cloud.


Repository Analyser

Every repository has some test cases are perfect for automation — they’re stable, repetitive, and save a huge amount of time when automated.

Repo Analyser helps you quickly identify these high-value tests, so you can focus on what brings the biggest impact with the least effort.

To start the analyser, select all the suites or test cases, and click 'Run Analyser' button:

The analysis will take a moment, so feel free to sit back or tackle other tasks. AIDEN will automatically notify you with a summary as soon as it’s done.

Let's understand the results:

Green: These test cases are easy to automate, with minimal or no oversight.
Yellow: Test case has good potential for automation, it may be missing information.
Red: This test case lacks essential details, such as test steps, or involves complex logic that makes automation challenging.

Based on the suggestions from AIDEN, once you edit your test cases that are not in Green, you can 'reanalyse' them.


Let's start automating!

Open any test case, and click the 'Automate with AI' button to begin:

Adding the environment

Your tests will run at a specific domain, so let's add the host environment:

If your host environment is not accessible from the public internet, you can help Qase tunnel to your private environment, here's a script that will help you set it up:

Authorization

Most of test cases generally require authorization as a precondition. You can add your authorization steps and use them when starting auto-test generation.

Generation

You can monitor the status and view the test case that is being used for generation at the top.

The generator works by first breaking down your manual test case steps into proper actionable steps.

A 'Success' or 'Failure' message is displayed for each step, along with a screenshot to communicate progress.

Edit Steps

If generation fails for a step, the status is updated as 'Error' and the particular steps with the problem will have the Error description.

You can help AIDEN by editing the particular step. Click 'Edit steps' and just correct the step text in natural language.

You can also delete steps that are not needed, or even edit steps that are successfully generated if you need to change something.

Click 'Regenerate' and AIDEN updates the steps. If you edit a step that is not generated yet, it will simply update the step's text.

If edits are made to a step that is already generated, it'll restart generation from that step.

Action Editor

For scenarios where the error is a bit complicated, for example, if an element is not recognized as a button, you can use the JSON Action Editor to debug the step.

Follow the link below to understand how the action editor works.

👉 Guide: Action editor

Notification widget

If you navigate away, to a different page in the middle of the generation. You can always check the progress from AIDEN's notification widget.

If the generation is successful, you can find the test case from the "For Review" tab.

Generation can also be paused. There's a tab to view all the test cases that are paused previously.

Review and Save

Once all test steps are successfully generated, the entire execution can be reviewed from the final step's attachment.

Click 'Save' to complete the generate and save the test case to the repository. You can differentiate this test case from the rest of the manual test cases with this symbol.

Executing the automated tests

To run the tests in Qase Cloud, simple select the tests from the repository for an express test run.

In this window, select 'Cloud' and proceed to choose the Environment, and Configuration options.

Depending on the browser configuration, multiple test runs will be created and the execution for the selected test cases will be begin the cloud immediately.

Once the tests are executed, the results will be posted back to the test run automatically.

A screenshot is captured at each test step along with a complete video of the entire execution, are attached to the result. You will also find a .zip file attached for the trace.

👉

https://github.com/qase-tms/qase-frp