CODEWITHSUNDEEP
origen-sdk
rchitect-of-info
rchitect-of-info

Reputation: 1586

post test execution callbacks available?

I am looking to apply a callback post test execution that will check for an alarm flag. I don't see any listed here so I then checked the test interface and only see what looks like a flow level callback:

# This will be called at the end of every flow or sub-flow (at the end of every
# Flow.create block).
# Any options passed to Flow.create will be passed in here.
# The options will contain top_level: true, whenever this is called at the end of a
# top-level flow file.
def shutdown(options = {})
end

We need the ability to check the alarm flags after every test but still apply a common group ID to a list of tests like this:

group "func tests", id: :func do
  [:minvdd, :maxvdd].each do |cond|
    func :bin1_1200, ip: :cpu, testmode: :speed, cond: cond
  end
end

Here is an example of the V93K alarm flow flag:

enter image description here

thx!

Upvotes: 0

Views: 44

Answers (1)

Ginty
Ginty

Reputation: 3501

It is common when writing interfaces to funnel all test generation methods through a common single method to add them to the flow:

def func(name, options = {})
  t = test_suites.add(name)
  t.test_method = test_methods.origen.functional_test(options)
  add_to_flow(t, options)
end

def para(name, options = {})
  t = test_suites.add(name)
  t.test_method = test_methods.origen.parametric_test(options)
  add_to_flow(t, options)
end

def add_to_flow(test_obj, options = {})
  # Here you can do anything you want before adding each test to the flow
  flow.test(test_obj, options)
  # Here you can do anything you want after adding each test to the flow
end

So while there is no per-test callback, you can generally achieve whatever you wanted to do with one via the above interface architecture.

EDIT:

With reference to the alarm flag flow structure you want to create, you would code it like this:

func :some_func_test, id: :sft1

if_failed :sft1 do
  bin 10, if_flag: "Alarm"
  bin 11, unless_flag: "Alarm"
end

Or, if you prefer, this is equivalent:

func :some_func_test, id: :sft1

bin 10, if_flag: "Alarm", if_failed: :sft1
bin 11, unless_flag: "Alarm", if_failed: :sft1

At the time of writing, that will generate something logically correct but with a sub-optimal branch structure. In the next release that will be fixed, see the test case that has been added here and the output it generates here.

You can call all of the flow control methods from the interface the same way you can from within the flow, so you can inject such conditions in the add_to_flow method if you want.

Note also that in the test case both if_flag and if_enable are used. if_enable should generally be used if the flag is something that would be set at the start of the flow (e.g. by the operator) and would not change. if_flag should be used if it is a flag that is subject to modification by the flow at runtime.

Upvotes: 1

Related Questions