TEST-TRACK 2.7

TEST-TRACK 2.7 (Released 11.05.2011)

• Cleaning up the database
  Possibility to remove boards from the database, including all associated test results and repair items. The removal can be done on the Track&Trace screen and is only allowed with administrator rights and when the board is not part of an order or packing list 

• Screen update
  All database tables can be refreshed at any moment by pressing F5 or using the menu View->Refresh. 

• Adding boards to Packing List
  Serial number field keeps focus so that numbers can be easily added with bar code scanner 

• Test conmmands
  New EOL modes for CONFIG_SERIAL, CONFIG_COM and CONFIG_TCP

TEST-TRACK 2.6

TEST-TRACK 2.6 (Released 01.12.2010)

• Improvements on test screen
  A number of improvements have been made concerning the execution and debugging of tests. It is now possible to execute a single test from the list of tests at the right of the screen by right-clicking on it. That test and any test in the test suite that are marked 'run always' are then executed. Furthermore, double clicking on a test will scroll the log screen to the start of the logging belonging to that test.
  
  It is now also possible to execute a test for a board that is not part of the currently active order line(s). This is useful for e.g. repair jobs. Until now, one had to find back the original order and unlock the order line on which the board appears. Testing boards that are in the database but not part of any order could not be tested at all in previous versions.After a number is entered that does not belong to the active order lines, then the system tries to find a board with that specified number of the type(s) that an be tested with the currently connected module. If there is more than one board type or more than one test suite associated to the module, the the user is asked to select the correct board type and/or test suite.
  
  Finally, the 'test without number' checkbox can be removed from the test screen via a new global option that is stored in the database and can only be modified by administrators.

• Test Suites
  Introduction of 'Postamble' scripts. Much like the Preamble script, a Postamble is executed AFTER the execution of every test script.
  See also the section about the TestEngine which lists some new predefined variables that are useful together with Postamble scripts

• Orders
  Boards that failed will now be added to an order if the corresponding global option is activated. This is a real global option in that it is stored in the database and therefore applies to all instances of TEST-TRACK. The option can only be changed by users with administrator rights.
  Besides the usual orders (which are now called Production Orders) this version introduces Sales Orders.
  When testing boards, the boards are assigned to a production order which can be seen as internal company orders: the boards are not necessarily assigned to a customer at this time (hence the option to also add failing boards to such an order) but are put on an internal stock. When a customer orders boards, a sales order is created on which boards from one or more production orders can be imported. The board remains on the original production order: a board can be associated to both a production order and a sales order.

• Packing lists
  The dialog for adding boards to an outgoing packing lists now also allows the import of 'any' test status instead of only tested, failed or untested.

• Miscellaneous
  In addition to modifying a table entry by selecting 'Modify' from the pop-menu, most tables now also support a double-click of the mouse.
  Finding back the order line (production or sales....) for a board is now easily done on the Track&Trace screen via the board table pop-up menu.
  Printing of labels is now optional and not 'hardwired' anymore to automatic serial number generation (board type administration dialog).
  Track&Trace: when searching on serial number, the system now implicitly adds wildcard characters around the specified number. E.g. specifying '123' will also find '1234' or 'A00123' if such numbers exist.

• Test Description Language
  The WAITRX and WAITTX commands got a new parameter that allows to specify the number of packet to wait for.
  The backslash character ('\') now has a special meaning: it is the 'escape character' that makes it possible to insert special non-printable characters (e.g. new-line, hexadecimal values) and other usually 'forbidden' characters like " in any string (including TRANSMIT_SERIAL).
  NOTE: some RUN commands in existing scripts may not work anymore if it contains path names that contain the backslash character. This can be easily fixed by replacing the backslash character with a 'normal' backslash '/' or by 'escaping' the backslash with a second backslash. See example 3 for the RUN command in section 4.9.3 of the Test Language Description document.
  Packets used in TRANSMIT_xx and RECEIVE_xx commands can now also contain binary values and the CR and/or LF characters at that used to terminate these packets are now optional. Instead, the RECEIVE_xx commands now offer the possibility to specify the number of bytes to be received. Variable substitution for transmit packets can now generate single byte or multi-byte binary values in either LSByte first of MSByte first format. The same applies to reception of packets. Besides converting values from ASCII, binary values can now also be assigned to variables.
  Finally, wildcards in receive commands are improved: the existing '*" can now be used anywhere in the packet (this used to be restricted to the end of the packet) and '?' is added to match exactly one character of byte.

• New predefined variables
  •#_ERROR_ which is set after test commandsExplained in 4.5.1
  TEST-TRACK Release Notes Page 5
  Revision: 2.7 Last modified: 11. May. 2011 18:13
  •#_TEST_FAILED_ which becomes true (1) as soon as a command in the current test fails
  •#_TEST_NR_ indicated the sequential number of the current test.The first test is 1.
  •#_NUM_OF_TESTS_ indicates the total number of tests in the test suite that is currently executed
  VAR declaration: variables can now be initialised with expressions.See 4.9.2

• Bug Fixes
  Several bugs were fixed, especially those that made the system crash when clicking on empty tables. Also fixed are some screen update problems.

TEST-TRACK 2.5

TEST-TRACK 2.5 (Released 01.06.2010)

• Test suites
  Test suites have become much more flexible. Until now, there was exactly one test suite
  associated with each TEST-OK module. Now, test suites have a name and more than one
  test suite can use the same module.
  Which test suite is used for testing is now determined by the order line.
  It is now possible to have more than one board type use the same TEST-OK module but
  each using its specific test suite(s). This is for instance useful if two versions of the same
  board exists that have the same physical test points but not the same specifications (e.g.
  one board type has not all components placed) .

• Global options are now test suite specific
  The options 'ask for visual check' and 'auto run' can now be set per test suite instead of
  globally.

• Full support for cover switch and integrated 230VAC - 2 x 24VAC powersupply system (option in the fixture).
  If the corresponding option is set for a test suite, a test cannot be started before the cover lid of the TEST-OK is closed. The test will also abort as soon as the cover lid will be opened during a running test session.
  This feature guarantees safety during tests in which 230VAC is involved (e.g. using the
  optional 2x24V AC supply). 

• Label printing
  Printing of a board label at the end of a test can now be configured independently of
  automatic serial number generation. Printing can be done automatically (for passed
  boards only or for any board) or manually.
  All these options can be found on the board type administration screen