From Business requirement to Unit Test,API Test & Integration Test

1. Integration Test (via UI)

Test Suite Setup

• Test Name: Provide a descriptive name (e.g. IntegrationTestExample).

• Test Type: Select Integration Test (options: Unit / Functional / Integration).

• Test Framework: Choose from supported frameworks:

  • Rest Assured

  • Karate (example used here)

  • Postman

• Selected Test Framework Version: Choose from supported versions
  
  
  
  

GenAI Models Setup

• Select AI Provider: Choose an AI provider (e.g. OpenAI, Vertex AI, Azure OpenAI, Claude, LLaMA).

  • Enter required credentials:

    • API Key / Token (from provider)
      

    • Model Name (e.g. gpt-4, claude-3, etc.)
      

  • Or choose connector 
    
    

Code Repository Setup

• Select Repository Type: GitHub, GitLab, Bitbucket, Azure Repos.

• Repository Details(Or choose connector):
  • Access Token / PAT: Token with valid permissions.
  • Username/Organization Name: for Azure/Bitbucket give username/organization name
    

• Branch: Branch where test PR will be created

• Project Path: Path for your project
  
  

Business Requirement Source

Integration with requirement management tools:

• Choose Source: Jira or Azure DevOps.

• Authentication:

  • Jira: Base URL, Email/Username, API Token.

  • Azure DevOps: Org URL, PAT token.

• Requirement Reference:

  • Provide Ticket ID (e.g. PROJ-1234) for Jira.

  • System will fetch business requirement details for context.
    
    

Gherkin Setup

• Gherkin Source: Choose how to provide acceptance criteria. Options:

  • File Upload: Upload .feature file.

  • URL: Provide direct URL to Gherkin spec.

  • Git Path: Specify repository and file path to .feature file.
    
    
    
    

Save the Test:

1. Once you have configured the test Save configuration and your test will be ready for the trigger

Test Execution

1. Click on execute test button to trigger the test
   
2. UI will prompt with Test Server Configuration details this provide the details and click on generate test
   
   
   
3. Test will be triggered after tokens are verified

4. Logs will be available in the UI in logs tab.
   
   

5. Once test creation is complete:

   • A Pull Request (PR) will be automatically generated in the selected repository.

   • PR link will be displayed.

   • You can view test insights from the generated PR.

     
     

Improving Tests

• Select the created test.

• Provide improvement instructions (e.g. “Add negative test for invalid payment ID”).

• Re-run improvement process.

• Updated PR will reflect the improved test suite.