[Question] TestRun custom fields

[spetrovi]

Hello, README.md mentions setting custom fields of TestRun via set_custom_field method which doesn't exist in TestRun class.

Should we use the available _set_custom_field method? Or is there some completely different way of populating custom fields od TestRun?

Thanks for answer, Sam

[leelavg]

Hi, currently afk so couldn't check my answer.

• Basically every work_item type will get autogenerated upon import of a specific work_item (like testrun, testcase etc)
• This is the reason you see a delay just after the import
• So, with TestRun creation all of custom_fields defined at global/project level will get attached to the created objected
• Then after, set/get calls can be directly performed on attrs

  # assume a custom field "component" exists, so..
  tr = TestRun(...)
  # get
  tr.component
  # set in cache
  tr.component= "dummy"
  # persist set cache
  tr.update()

• Most, if not all value types (enum/arrayOfEnum etc..) will be mapped to python virtual obj automatically

[spetrovi]

Wow, amazing, this works for me!

The Examples should maybe be updated, though.

Thanks for help, Sam