origen_testers 0.40.0 → 0.41.0

data/templates/origen_guides/program/flowapi.md.erb

@@ -67,6 +67,66 @@ if_enable :word1 do
 end
 ~~~
 
+
+#### Execution Based on Relational Expressions
+
+The following methods are available to describe these cases:
+
+* **whenever** - Run the test(s) if the relational expression evaluates to TRUE
+* **whenever_all** - Run the test(s) if ALL of the relational expressions evaluate to TRUE
+* **whenever_any** - Run the test(s) if ANY of the relational expressions evaluate to TRUE
+
+The following relational operators are available for use with the above methods:
+
+* **eq** - equal to
+* **ne** - not equal to
+* **gt** - greater than
+* **ge** - greater than or equal to
+* **lt** - less than
+* **le** - less than or equal to
+
+Here are some examples of how to apply these methods:
+
+~~~ruby
+# Run these tests if VAR1 is greater than 2
+whenever gt(:var1, 2) do
+  func: :test1
+  func: :test2
+end
+
+# Run these tests if VAR1 is greater than 2 AND VAR2 is less than VAR3
+whenever_all gt(:var1, 2), lt(:var2, :var3) do
+  func: :test1
+  func: :test2
+end
+
+# Run these tests if VAR1 is greater than 2 OR VAR2 is less than VAR3
+whenever_any gt(:var1, 2), lt(:var2, :var3) do
+  func: :test1
+  func: :test2
+end
+~~~
+
+Additionally, these variables can be set in the flow using the **set** method as shown in here:
+
+~~~ruby
+# Set the VAR1 = 1
+set :var1, 1
+set :var2, 'OFF'
+set :var3, 3.14
+
+# Update VAR1 value based on some runtime condition
+if_enable :some_other_variable do
+  set :var1, 3
+end
+
+# Run these tests if VAR1 is greater than 2
+whenever gt(:var1, 2) do
+  func: :test1
+  func: :test2
+end
+~~~
+
 #### Execution Based on a Previous Test
 
 The following methods are available to describe these cases:

data/templates/origen_guides/program/interface.md.erb

@@ -236,7 +236,7 @@ def add_to_flow(test_object, options = {})
 end
 ~~~
 
-Finally, a convenience method exists that will trigger if either the context or one of your
+Also, a convenience method exists that will trigger if either the context or one of your
 specified parameters changes:
 
 ~~~ruby
@@ -244,5 +244,38 @@ if context_or_parameter_changed?(:vdde, :vddc, options)
   # ...
 ~~~
 
+#### Reloading of the Target
+
+By default, Origen reloads the target whenever a new flow file (top level or sub-flow) is encountered.  This can lead to
+increased flow generation time if the flow is large and calls many sub-flows.  To turn off reloading of the target, configure
+the test interface to set the attribute `reload_target` to `false`.  Here is an example from the origen_testers spec tests:
+
+~~~ruby
+class MyInterface
+  include OrigenTesters::ProgramGenerators
+
+  attr_accessor :reload_target
+
+  def initialize(options = {})
+    @reload_target = false
+  end
+end
+
+This feature also exists at the flow file level, however the test interface will take precendence.  For example, the following flow file option
+will not have any effect if the test interface has the `reload_target` attribute set to `false`.
+
+~~~ruby
+Flow.create interface: 'MyInterface', reload_target: true do
+  # Tests inserted here
+end
+~~~
+
+If the test interface does not set the `reload_target` attribute to `false`, then a flow file may do so to prevent reloading of the target.
+
+~~~ruby
+Flow.create interface: 'MyInterface', reload_target: false do
+  # Tests inserted here
+end
+~~~
 
 % end

data/templates/origen_guides/program/j750.md.erb

@@ -550,6 +550,42 @@ to prevent Origen from trying to match up the flow with an instance object.
 flow.test("POR_INSTANCE", instance_not_available: true)
 ~~~
 
+### Multi-site Flow Control
+
+The [common flow-control API](<%= path "guides/program/flowapi/#Execution_Based_on_a_Previous_Test" %>) will generate
+content into the IG-XL flow sheet's *device* columns, meaning that the flow execution branching will be specific to each site.
+
+However, IG-XL also provides the ability to control test execution based on the test results across multiple sites via
+the *group* columns and Origen provides some additional IG-XL-only APIs to work with that feature.
+
+The following flow-control options/methods are available which can be used in the same way as the common site-level
+options such as `if_failed`, `if_passed`, etc:
+
+* **if_any_sites_failed** - Run the test(s) on all sites if ANY site failed the referenced upstream test
+* **if_all_sites_failed** - Run the test(s) on all sites if ALL sites failed the referenced upstream test
+* **if_any_sites_passed** - Run the test(s) on all sites if ANY site passed the referenced upstream test
+* **if_all_sites_passed** - Run the test(s) on all sites if ALL sites passed the referenced upstream test
+
+These inverse forms are also available:
+
+* **unless_any_sites_failed**
+* **unless_all_sites_failed**
+* **unless_any_sites_passed**
+* **unless_all_sites_passed**
+
+Here is an example of how to use in both block and in-line forms:
+
+~~~ruby
+func :read1, id: :ta1, bin: 10, number: 60000
+func :erase1, if_any_site_failed: :ta1, bin: 12, number: 60010
+
+func :read2, id: :ta2, bin: 10, number: 60020
+if_any_site_failed :ta2 do
+  func :erase2, number: 60030
+  func :erase2, number: 60040
+end
+~~~
+
 ### What About My DC Specs?
 
 Other IG-XL sheets do not currently have generators available, although that is likely

data/templates/origen_guides/program/v93k.md.erb

@@ -144,6 +144,9 @@ module Vreg
         my_test: {
           # [OPTIONAL] The C++ test method class name can be overridden from the default like this:
           class_name:   'MyTestClass',
+          # [OPTIONAL] If the test method does not require a definition in the testmethodlimits section
+          #    of the .tf file, you can suppress like this:
+          render_limits_in_file: false,
           # Parameters can be defined with an underscored symbol as the name, this can be used
           # if the C++ implementation follows the standard V93K convention of calling the attribute
           # the camel cased version, starting with a lower-cased letter, i.e. 'testerState' in this

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: origen_testers
 version: !ruby/object:Gem::Version
-  version: 0.40.0
+  version: 0.41.0
 platform: ruby
 authors:
 - Stephen McGinty
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2019-07-24 00:00:00.000000000 Z
+date: 2019-08-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: origen
@@ -488,8 +488,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.7.7
+rubygems_version: 3.0.4
 signing_key: 
 specification_version: 4
 summary: This plugin provides Origen tester models to drive ATE type testers like