Q7

String-keyed properties for assertion

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.3.10
  • Fix Version/s: 1.3.10
  • Component/s: Runtime, UI
  • Labels:
    None
  • Test Mode:
    Manual

Description

Currently 'multi-valued' properties are indexed only by number, however it could be great to support string keys

This issue consists of two parts:

  1. Provide basic mechanism for string-valued props
  2. Add 'values' property to tree/table items, which would hold cell values indexed by column name:
    get-item "Foo" | get-property "values[Resource]" | equals Program.java | verify-true
    

Activity

Hide
Stanislav Belyakov added a comment - 12/Dec/13 6:34 PM

There is a problem with property path building. For example, in assertion mode when we obtain table item value through table (using advanced properties, i.e. reflection), q7 record this code: get-table | get-property "getItems().TableItem[0]". This path is incorrect and correct property path should be "getItems()[0]". Q7 makes correct property path for tesla model properties (like get-table | get-property "columns[0].selection" ).

Show
Stanislav Belyakov added a comment - 12/Dec/13 6:34 PM There is a problem with property path building. For example, in assertion mode when we obtain table item value through table (using advanced properties, i.e. reflection), q7 record this code: get-table | get-property "getItems().TableItem[0]". This path is incorrect and correct property path should be "getItems()[0]". Q7 makes correct property path for tesla model properties (like get-table | get-property "columns[0].selection" ).
Hide
Stanislav Belyakov added a comment - 13/Dec/13 1:39 PM

Feature added.

Show
Stanislav Belyakov added a comment - 13/Dec/13 1:39 PM Feature added.

People

Vote (0)
Watch (0)

Dates

  • Created:
    06/Dec/13 3:39 PM
    Updated:
    15/Jan/14 5:27 PM
    Resolved:
    13/Dec/13 1:39 PM