Attributes, tags, and environments
Attributes, tags, and environments enable you to:
Test your release and product comprehensively by running the same test in different environments. For example, you might want to track the quality of your release in a Windows environment and also in a UNIX environment.
Filter lists by attributes, tags, and environments, so you see only relevant information.
Analyze quality by creating dashboard and overview graphs that are based on a specific set of attributes, tags, and environments.
Attributes are predefined characteristics for a particular item. These are the fields available for each item, and each field can have a value.
|Phase||New, Opened, Awaiting Review, Ready...|
|Item type||Pre-Release, Business...|
|Test type||Regression, End to End ...|
|Severity||Low, Medium, Urgent...|
|Testing tool||Manual, Selenium, UFT, LeanFT, StormRunner, LoadRunner ...|
|Run status||Skipped, Passed, Failed...|
Tags are special types of attributes. Tags are user-defined and can be used to label an item as "something."
You do not specify a value for a tag. Instead, tags are used more like a label or a flag on an item.
Create a tag called FutureCandidate. Any user story or defect tagged as FutureCandidate is likely to be postponed to a future release if time runs out.
Create a tag called HighRisk. Any user story tagged as HighRisk is one that could impact many features and should be handled by an experienced developer.
Tags let you filter information you see on any value you like—not just the supplied attributes that ALM Octane assumes are most popular. Furthermore, you can search in more specific ways with these individual tags.
Unused tags are automatically deleted by the system after a while.
For details on adding tags, see Label items by adding tags.
Environments are special types of tags. Environments are user-defined, but more structured than tags because:
An environment is assigned a value.
An environment is generally used to describe the environment for testing your AUT.
You can customize the environment values for certain operating systems, browsers, databases, and so on.
Environments let you filter information you see on any value you like—not just the attributes that ALM Octane assumes are most popular.
|Test objectives||Beta testing, stress testing, security testing|
|Deployment environment||QA, staging, production|
|Browser||Internet Explorer, Firefox, Chrome|
|Browser version||9.0, 5.0, 10.00|
|Test framework||JBehave, Cucumber|
|Operating system||Linux, Windows|
|Operating system version||7.0, 10.00|
|Packaging / distribution type||On-premise, SaaS, OEM|