Uploaded image for project: 'Xray for Jira Cloud'
  1. Xray for Jira Cloud
  2. XRAYCLOUD-10596

GenAI: Automated Script Generation should support Typescript

    XporterXMLWordPrintable

Details

    • Suggestion
    • Status: New
    • Resolution: Unresolved
    • None
    • None
    • None
    • UNCOVERED

    Description

      Description
      Currently, Xray AI Test Script Generation supports Selenium and Playwright frameworks using Java and Python languages only. However, it does not support TypeScript, which is a primary language for modern Playwright-based automation.

      We propose enhancing the AI Test Script Generation feature to add TypeScript support, enabling broader adoption and reducing friction for teams standardized on the JavaScript/TypeScript ecosystem.

      User friction
      Users who rely on Playwright with TypeScript cannot directly use the AI-generated test scripts. This forces them to either:

      • Manually rewrite generated scripts into TypeScript, or
      • Switch to unsupported languages solely to use the AI feature

      This breaks workflow continuity and significantly reduces the value of AI-driven test generation.

      Steps to reproduce (right now) / Actual Result:

      • Open Xray and navigate to AI Test Script Generation
      • Select Playwright as the automation framework
      • Attempt to choose TypeScript as the scripting language

      Actual Result:
      TypeScript is not available as a language option. Only Java and Python are supported.

      IMPACT

      • Prevents adoption of AI features by teams using Playwright + TypeScript
      • Increases manual effort and error-prone script translation
      • Reduces competitiveness compared to tools that support TypeScript-first workflows
      • Limits usability for frontend-heavy teams where TypeScript is the default

      What would improve if solved:

      • Users can directly generate Playwright TypeScript test scripts using AI
      • Faster test creation with reduced manual intervention
      • Higher accuracy and consistency in the generated test automation
      • Improved overall developer and QA experience

      Impact on stakeholders:

      • QA Engineers: Reduced scripting effort and faster automation
      • Developers: Alignment with existing TypeScript codebases
      • Product Teams: Increased feature adoption and customer satisfaction
      • Business: Broader market reach and stronger competitive positioning

      Current workaround:

      • Generate test scripts in Java or Python
      • Manually rewrite them into TypeScript
      • Validate syntax and framework compatibility manually

      CONTEXT & EXAMPLES:
      TypeScript has become the default language for Playwright, especially for web applications built using modern frontend frameworks like React, Angular, and Vue.

      Many organizations standardize on TypeScript-only automation, making the current AI feature inaccessible without additional rework.

      Concrete example:
      A QA team using Playwright + TypeScript wants to generate a login test using AI.
      The AI produces a Java-based Playwright script, which the team must:

      • Rewrite into TypeScript
      • Adjust async/await syntax
      • Modify assertions and locators for TypeScript conventions

      This negates the productivity gains promised by AI test generation.

      Workaround risk:

      • Manual translations introduce syntax and logic errors
      • Inconsistent test implementations across teams
      • Increased maintenance cost
      • Discourages the usage of AI features altogether

      Attachments

        Activity

          People

            Unassigned Unassigned
            jayanthi.murthi Jayanthi Murthi
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated: