QATTS Technical Docs
V 2.0
V 2.0
  • QATTS Product Documentation
  • 1.Getting Started
    • 1.1 About QATTS
    • 1.2 QATTS Terminology
  • 2. QATTS Configuration
    • 2.1 Adding Product
    • 2.2 Create Code Branch
    • 2.3 Create Client
    • 2.4 Create Deployment
    • 2.5 Configure Execution Nodes
    • 2.6 Configure Tools
    • 2.7 Create Roles
    • 2.8 Create Users
    • 2.9 Manage Configuration
      • 2.9.1 Manage Product
      • 2.9.2 Manage Code Branch
      • 2.9.3 Manage Client
      • 2.9.4 Manage Deployment
      • 2.9.5 Manage Requirements
      • 2.9.6 Manage Workflows
      • 2.9.7 Manage User
      • 2.9.8 Manage Milestones
      • 2.9.9 Manage Tools
  • 3. Test Script development
    • 3.1 Manual Test Script development
      • 3.1.1 Create Manual Functionality
      • 3.1.2 Adding Test Case
      • 3.1.3 Adding Test Data
    • 3.2 Automated Test Script Development
      • 3.2.1 Adding Object Groups
        • 3.2.1.1 Create UI Elements
        • 3.2.1.2 Create Product Element
        • 3.2.1.3 Create API Objects
          • 3.2.1.3.1 API Parameterization
          • 3.2.1.3.2 Data Extraction
          • 3.2.1.3.3 Data Assertion
        • 3.2.1.4 Create Query
        • 3.2.1.5 Create Smarty
      • 3.2.2 Adding Functionalities
        • 3.2.2.1 Create Functionality
        • 3.2.2.2 Adding Test Script (Action Class)
  • 4. Test Execution
    • 4.1 Manual Test Execution
      • 4.1.1 Creating Test runs
      • 4.1.2 Assign for Test Run
    • 4.2 Automated Test Execution
      • 4.2.1 Creating Test Runs
      • 4.2.2 Scheduling Test Runs
  • 5.Test Results/ Reports
    • 5.1 Test Results/Reports
  • 6. Manage Features
    • 6.1 Create Feature
    • 6.2 Create Build
    • 6.3 Create Milestone
  • 7. FAQs
    • Untitled
  • 8. References
    • 8.1 Video Tutorials
  • 9. How to - Guides
    • 9.1 How to Automate Web Application
    • 9.2 How to Automate Mobile Application
    • 9.3 How to Automate API
    • 9.4 How to Automate Desktop Applications
Powered by GitBook
On this page

Was this helpful?

  1. 4. Test Execution
  2. 4.1 Manual Test Execution

4.1.2 Assign for Test Run

Previous4.1.1 Creating Test runsNext4.2 Automated Test Execution

Last updated 3 years ago

Was this helpful?

Assigning test steps to tester

  • Click on the show bulk update toggle button. You will get the below screen.

  • Select the select column drop down as tester

  • After select the select column as tester you will get the list of users in select column value drop down.

  • Select the tester and then select the Apply to drop down.

  • Now click on the update button. Selected tester will assign to the testers.

Execution of Testcase

  • After assign the steps to the tester. Tester needs to start the execution.

  • To start the execution of the test case, click on the play icon. You will navigate to step result info page.

  • In the step result info page, you will see complete description of the test case and input data and output data.

  • Click on the doc symbol input data will be displayed.

  • Check the output variables weather it is pass/fail if the output data is equals to expected data, then set the output data pass otherwise fail.

  • Click on the comments tab.

  • Here you can share the screen shots and comments regarding the test case.

  • After complete the test case give the duration time and click on select the result.

  • When you update the result, status was updated automatically based on result.

  • After update result to the step manager is review the step and he Approve/Reject the step.

  • After Approved/Reject the step status is updated to approved or rejected.

  • If any test case is failed you will get option to create the JIRA ticket for the test case.

  • When you click on the plus symbol JIRA ticket will be created and displayed ticket number.

  • After completion of the all the test cases click on the “Complete” button.

  • Now you can see the confirmation pop-up. Click on the Complete. Now your test run completed successfully.