Description

In the GenRocket web platform, within a given Project Version, Attributes may reference other Attributes in three primary levels:

  • Domain Level - Within a Domain, an Attribute may reference other Sibling Attributes. However, Domains are loosely coupled to each other at the Domain level. At the Domain level, parent, child, and sibling relationships can be defined, but the relationships are conceptual and not concrete. Thus, at the Domain level, Attributes cannot reference other Attributes outside of their own Domain.

  • Scenario Level - Within a Scenario, the parent, child, and sibling relationships, which were defined conceptually at the Domain Level, are concrete at the Scenario level within Scenario Domains. Thus, at the Scenario level, Attributes can also reference Attributes from within other sibling Scenario Domains.

  • Test Data Case Level - Within a Test Data Case, Domains are global to each other within a given Project Version. The relational coupling between Domains is loose because Test Data Case Domains are not associated with any Scenario and can only dynamically alter a given Scenario at runtime.

The three levels of Attribute referencing, described above are very flexible and useful for most testing scenarios. However, there are testing scenarios that involve organization-level challenges where Attributes need to reference other Attributes, where Domains are not directly related to each other, or relationships between Domains cross Project level boundaries. This is where Organization Attributes come into view and can be used to solve this Test Data Challenge.


In This Article


Attribute Referencing at the Organization Level

Organization Attributes provide a way to reference an Attribute at the Organization Level. Organization Attributes allow an Attribute's generated value to be referenced by multiple Projects without the need to perform the same steps to configure the Attribute in each Project. Users can set up a collection (suite) of Organization Attributes with their own Generator configurations and then reference them via Test Data Cases as needed. 

 


What is an Organization Attribute Suite? 

  • A collection of Organization Attributes. 


What are Organization Attributes? 

  • An Attribute containing one or more assigned Generators that can be referenced at the Organization Level.

When Should Organization Attributes Be Used?

  • When the generated value needs to be referenced by multiple Projects within the Organization. 

  • This allows the Attribute to be referenced across Projects by multiple users without having to define the Attribute within each Project. 

How to Access Organization Attributes

  • Expand the Management Menu in the Menu Bar and select Organization Attributes



Simple Use Case

A user needs to set up an Attribute that uses Linked Generators to generate a unique Code. Multiple Projects require the code, and the configuration takes a lot of time to set up for each Project. 


Instead, the user set up an Organization Attribute with the linked Generators to generate the required code value. 

This allows any Attribute created within a Test Data Case Domain to reference the Organization Attribute, code, without having to set up all the Generators each time for each Project/Project Version. 


Additionally, all Attributes referencing the Organization Attribute will produce the same exact values.

 

How Do Organization Attributes Work?

  1. Create an Organization Attributes Suite.
  2. Add one or more Organization Attributes. 
  3. Add one or more Generators to each Organization Attribute. 
  4. Select any Generator to make changes to its Parameters. 
  5. Reference the Organization Attribute in each Project. 

 

User Case Examples

TopicDescription
Organization Attributes Step-By-Step Example
See a step-by-step example of setting up a single Organization Attribute with Linked Generators. 


"How To" Articles

TopicDescription
How do I add Generators to an Organization Attribute?Learn how to add one or more Generators to Organization Attributes. 
How to copy a Domain Attribute to the Organization Attribute Level
Learn how to copy an Attribute at the Domain Level to the Organization Attribute level.