Aligned Elements Web Client User Manual
3.1.272.24402
3.1.272.24402
  • Introduction
  • Basic Concepts
  • Get Started
    • Activate your Aligned Elements Account
    • Log In
    • Open a Project
    • Change Project
    • Create a new Project
    • The Project Start Site
    • Your Assigned Items
    • Manage Your User
    • Log Out
    • Enter Design Control Items
      • Work with Chapters
      • Work with Table Attributes
      • Inserting Images in Attributes
      • Working with Traces
      • Add Issues
      • Add Attachments
      • Collaborate using Comments
      • Favourites
      • Find in... Actions
      • Inconsistencies and Positive Cues
  • Document Object Actions
    • Move and Rearrange Chapters and Document Objects
    • Update Multiple Items
    • Generate Design Control Items
    • Copy Design Control Items
    • Lock Document Objects
    • Generate Reports
    • Export Document Objects
    • Import Document Objects
    • Copy Document Objects between Projects
    • Import Files
  • Explorers and Views
    • Project Explorer
    • File Explorer
    • Trace Explorer
    • Test Run Explorer
    • Project History
    • Chapter View
    • List View
    • Search Result View
    • Export to Excel in Grids
  • Project Status
    • Display Inconsistencies
    • Display Consistency Coverage
    • Display Risk Summary
    • Display DHF Index
  • Queries
    • Run a Query
    • Design a Query
    • Query Filters
  • Charts
    • Display a Chart
    • Design a Chart
  • Trace Tables
    • Run a Trace Table
    • Design a Trace Table
  • Work with Documents
    • Adding Word Document to File Objects
    • The Word Add-in. Adding Design Control Items to Documents
    • Sign Documents with Electronic Signatures
    • Save Files to Disk
    • Released Document View
  • Design Reviews
    • Conduct a Design Review
  • Risk Analysis
    • Perform a FMEA Risk Assessment
    • Perform a Preliminary Hazard Analysis
    • Relative vs. Absolute Mitigations
    • Potential Hazard
    • Using the Risk Analysis to assess the Software Safety Classification
  • Manage Tests
    • Test Runs
      • Planning a Test Run
        • The Burndown Chart
      • Executing a Test Run
      • Completing a Test Run
      • Test Run Functions
      • Test Runs and Linked Projects
      • Caching of Test Runs and Test Run Explorer
    • Classic Tests
  • Work with Tags
    • Add Tags
    • Filter views on Tags
    • Edit Tags
    • Tags and Snapshots
  • Assistants
    • Run an Assistant
  • Snapshots
    • Create a Snapshot
    • Display a Snapshot
    • Compare Snapshots
  • Settings
    • Project Information
    • Manage Users
    • Manage User Groups
    • Project Settings
    • Project Hierarchy
      • Branch Projects
      • Merge Projects
    • Unlock Objects
  • Dashboards
    • Select a Dashboard
    • Create a Dashboard
    • Remove a Dashboard
  • AI Features
    • AI Features in Aligned Elements
  • Aligned Elements Automation Tool
    • The Automation Tool
  • Web Administrator Tools
    • Manage Projects
    • Rename, Copy or Remove Project
    • Manage Users
    • Manage Permissions
    • Register a new Administrator
    • Inspect User Logs
    • Manage Templates
    • Download Log Files
  • Manage Service Configuration
  • Configure a Type Name Change
Powered by GitBook
On this page
  1. Manage Tests

Classic Tests

Aligned Elements Classic tests imply that an Executed Test Case Document Object is created when a Test Case is executed. The ID number of the Executed Test Case will be the same as the ID number of the Test Case.

When the same Test Case is executed a second time, a new Revision is created of the Executed Test Case. Thus, a Test Case can have a maximum of one result (the Executed Test Case) at any given time.

The Test Run feature cannot be mixed with the Classic Tests due to ID designation of the executed test cases.

How to Execute a Classic Test Case

To execute a Test Case document object and create an Executed Test Case, follow these steps:

  1. Open a Test Case in the Document Object Form. Select Execute in the Actions dropdown and select the type to create.

  2. This will create a new Executed Test Case where the ID number is identical to the ID number from the Test Case. A trace is also created from the Test Case to the Executed Test Case (equivalent to Generate Document Object). Also, all attributes that are common to the parent Test Case have been copied to the Executed Test Case. After having created the Executed Test Case, the Execution number will be equal to “1” (first execution of the Test Case).

  3. Follow the test case instructions and fill out the additional fields in the Executed Test Case.

  4. When you are done with the execution of the Test Case, you can store your new data by clicking Save.

  5. You can continue working on an Executed Test Case by opening it again. Any changes will be stored as a new revision but the Execution No will remain.

  6. If the execution is completed and successful, set the status to Passed (or equivalent). If the execution was not successful, set the status to Failed (or equivalent).

To re-execute a Test case (the Test Case has already been executed at least once):

  1. Open a Test Case in the Document Object Form. Select Execute in the Actions dropdown and select the type to create.

  2. This will create a new revision of the existing Executed Test Case. Also, all attributes that are common to the parent Test Case have been copied to the Executed Test Case and any specific Executed Test Case attributes are left blank. The Execution number will be increased by one.

  3. Continue working as when you executed the test case the first time.

When filling out the test case, you can take advantage of the large number of available column types in the Table Attribute.

E.g., use a CheckBox column to set results or a trace column to create/refer to issues for found product anomalies on the fly.

PreviousCaching of Test Runs and Test Run ExplorerNextAdd Tags