Select Semiconductor Module » Import Test Limits into <filename> to import test limits from a tab-delimited test limits text file into all test steps in a sequence file at edit time. When you import test limits from a text file, you can replace only the tests defined in the test limits file or you can delete all the tests in the sequence file and recreate each test from the contents of the test limits file.

The Import/Export Test Limits tool uses the SequenceName, StepName, and StepId columns in the test limits file to match tests in the sequence file. When you update the limits in matching tests from the test limits file, the tool also uses the TestNumber column to identify the test. If one of these identifier columns does not exist in the test limits file, the tool imports data into any step or test that matches the remaining identifiers and a row in the test limits file might update multiple locations in the sequence file. If more than one location in the sequence file matches the identifiers in a row in the test limits file, TSM imports data from that row into all the matching locations.

When you assign a base test limits file for a test program, importing a test limits file will automatically merge the values of the base file, overriding or inheriting values accordingly. TSM imports the merged values.

The Import/Export Test Limits tool returns an error and fails to import a test limits file if:

  • A row in the test limits file does not match any location in the sequence file.
  • A single test in the sequence file matches more than one row in the test limits file.
  • A location in the sequence file does not match any row in the test limits file and the Require every step to be in test limits file option is enabled.
  • A row in the test limits file matches a Semiconductor Sequence Call step in the sequence file and the Test Data Source column contains a value.
  • There is a base test limits file assigned for the test program, and the base test limits file contains any <inherit> values.
  • There is a base test limits file assigned for the test program, and the test limits file being imported has a unique test with one or more <inherit> values, but that unique test is not found in the base file.

The Import Test Limits into Sequence File dialog box contains the following options:

  • Update limits in matching tests—Finds any test in the sequence file that matches the SequenceName, StepName, StepId, and TestNumber identifier columns in the test limits file and sets the property values in the sequence file to the corresponding values in the test limits file. If one of these identifier columns other than TestNumber does not exist in the test limits file, the tool sets the corresponding property values for any step that matches the remaining identifiers.
    Note You cannot change the test number for tests in the sequence file when you select this mode. You must use the Replace all tests in matching steps option if you want to change the test number.
    The tool modifies only the tests and properties that exist in the test limits file. Tests and properties defined in the sequence file but not in the test limits file remain in the sequence file unchanged. Select this option when you want to set only certain test properties at run time.
  • Replace all tests in matching steps—Deletes all the tests that correspond to steps in the test limits file and recreates each test from the contents of the test limits file by adding tests to any step that matches the SequenceName, StepName, and StepId identifier columns in the test limits file. If one of these identifier columns does not exist in the test limits file, the tool adds a test to any step that matches the remaining identifiers. For columns that do not exist in the test limits file, the tool sets the corresponding property to the default value in the sequence file. The test limits file must include the columns in which you use non-default values; otherwise, the tool uses default values for those properties in the sequence file. If any step in the test limits file has a value of No Tests for the Test Number, the tool deletes all tests for any matching steps.
    Note Use the Semiconductor Action step instead of the Semiconductor Multi Test step if the step does not contain any tests.
    Select this option when you want to use limit files with different numbers of tests. For example, you might want to include more tests in a normal testing mode than you include in a QA testing mode.
  • Require every step to be in test limits file—Returns an error and does not import the file if a test or step exists in the sequence but does not exist in the limits file. If you do not enable this option, the Import/Export Test Limits tool returns a warning and imports only matching tests or steps in the limits file.