staxhistory2x.php
来自「Software Testing Automation Framework (S」· PHP 代码 · 共 776 行 · 第 1/3 页
PHP
776 行
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head> <title>Software Testing Automation Framework (STAF)</title></head><body><?phprequire "top.php";require "navigate.php";?><!-- Insert text for page here --><tr><td><center><h1>STAX History</h1></center><PRE>-------------------------------------------------------------------------------History Log for STAX Legend: - Fixes + Features = Internal changes * Changes required to migrate from one release to another-------------------------------------------------------------------------------Version 1.5.10: 04/18/2006 - Fixed problem calling a function like has_key() directly on a STAXGlobal instance without having to call it's get() method first (Bug #1408579)-------------------------------------------------------------------------------Version 1.5.9: 12/07/2005 - Fixed problem where the Monitored green ball icon was sometimes not displaying correctly in the STAX Monitor (Bug #1262534) - Fixed NullPointerException when listing threads or querying threads for a job that doesn't have any threads running (Bug #1329497) - Fixed NullPointerException that can occur in an error situation when running the STAX Monitor (Bug #1330198)-------------------------------------------------------------------------------Version 1.5.8: 08/15/2005 - Fixed problem in <loop> where the until expression was being evaluated at the top of each loop instead of at the bottom of each loop (Bug #1196936) - Added STAX Extensions File DTD to the STAX zip/jar file (Bug #1216745) - Fixed StringIndexOutOfBoundsException that occurs in STAX Monitor window if STAF is shutdown without first stopping the STAX Monitor (Bug #1029520) - Fixed some typos in STAX User's Guide for <process> example (Bug #1238388) = Changed to not use enum as a Java variable name so can compile using Java 5.0 since enum is now a Java keyword (Bug #1241613) - Fixed problem in STAXUtil.xml's STAFProcessUsing function to handle redirecting stderr to stdout corrrectly (Bug #1247056) - Fixed problem where multi-line Job results were not displayed correctly in the STAX Monitor (Bug #1256760) - Fixed problem where the job result may not be None if an error occurs evaluating the value for a <return> element (Bug #1257026)-------------------------------------------------------------------------------Version 1.5.7: 05/05/2005 - Fixed problem in STAXUtilExportsSTAFVars function handling variables containing double quotes (Bug #1114317) - Use default STAX Monitor properties if the monprp.ser file is corrupted (Bug #1118227) = Changed to use Xerces2-J 2.6.2 as the XML parser (Feature #1045560) = Removed the zxJDBC code from our distribution of Jython (Bug #1118221) - Changed resolve variable method to check for occurence of "{" anywhere in a string instead of just in the first position (Bug #1151440) - Fixed so that STAXPythonEvaluationErrors for 'STAXPyEvalResult =' no longer occur (Bug #1158649) - Changed license from GPL to CPL for all source code (Bug #1149491) - Changed to handle STAXGlobal list objects in the iterate/paralleliterate elements without specifying the get() method (Bug #1156045) - Changed to use Monospaced font for text areas in the STAX Monitor where Python code is specified (Bug #1163364) - Fixed problem using STAX Monitor's Job Wizard where if you enter more than one line of text for an argument, lines 1-n are not saved (Bug #1164120) - Fixed problem resubmitting a job via STAX Monitor if select "Local machine" for the Script File Machine (Bug #1164868) - Fixed STAX Monitor Job Wizard problems with saved function arguments (Bug #1190449) - Document that the STAX Service requires Java 1.4 or later (Bug #1192762) - Fixed typo in the STAX User's Guide for a <job> example (Bug #1195335) -------------------------------------------------------------------------------Version 1.5.6: 01/26/2005 - Fixed job hang problem that could occur if a Python evaluation error occurs evaluating a list such as iterate's "in" attribute (Bug #1075469) - Fixed race condition in call element (Bug #1073774) - Fixed NullPointerException if STAX VERSION request fails due to problem accessing the STAX service machine (Bug #1105669) - Fixed STAX Monitor Job Wizard errors in generating function argument values (Bug #1042460) + Provided two new Python variables, STAXJobStartFunctionName and STAXJobStartFunctionArgs (Feature #1110050) -------------------------------------------------------------------------------Version 1.5.5.1: 11/06/2004 - Retry querying STAX logs without the ALL option to avoid an error if the STAX service is on a STAF V2.6.5 or earlier machine (Feature #1040232)-------------------------------------------------------------------------------Version 1.5.5: 11/05/2004 - Fixed typo to specify function-no-args, not function-no-arg, in STAX User's Guide (Bug #1003544) - Fixed typo for loop example in STAX User's Guide (Bug #1004127) - Fixed STAXThread::pyListEval() to handle single item better (Bug #1017855) - Fixed so that a command parsing error on an EXECUTE request returns RC 7, "Invalid Request String", instead of RC 1, "Invalid API" (Bug #1020590). - Fixed location substitution for 'local' for a stafcmd when it's details are displayed in the STAX Monitor (Bug #1033015) - Fixed problem iterating Java list objects (Bug #1043148) + Added condition stack to output when querying a STAX thread for help in debugging problems (Feature #1054755) + Changed to specify the ALL option when querying a STAX log in order to get all the records that meet the query criteria in case the LOG service limits the default maximum records returned on a QUERY request (Feature #1040232) - Fixed problem re-selecting rows in the STAX Monitor Active Processes and Active STAFCmds tables (Bug #1061183)-------------------------------------------------------------------------------Version 1.5.4: 07/21/2004 + Added un-register of the service handle during term() (Feature #966079) - Fixed NumberFormatException in STAXTestcase.addElapsedTime (Bug #974925) + Added a STAXJobScriptFiles variable (Feature #977071) - Fixed "TypeError: call of non-function" problem where a job would log this error and hang if a variable named "type" was assigned in a job since the STAX service uses the Python built-in function named "type" (Bug #981435) - Fixed memory leak running a sub-job (Bug #981548) - Changed to use upper-case STAX service name when setting the STAXJobUserLog variable and in the STAX Monitor (Bug #982163) + Added new Python variables for the STAX service name/machine and the Event service name/machine (Feature #982109) + Made some usability enhancements when setting STAX Monitor properties: - Automatically update Event machine/service based on the specified STAX service's Event settings Note: Can no longer edit Event machine/service property fields - Allow local to be specified for the STAX Service machine (Feature #987502) - Fixed problem where <defaultcall> passed None to the function if no arguments were specified (Bug #991804)-------------------------------------------------------------------------------Version 1.5.3: 05/26/2004 + Updated to use XML Parser for Java (Xerces) version 1.3.0 (Feature #931256) + Updated to record more info from exceptions when parsing (Feature #931415) - Fixed problem where job would hang if called a function passing too many map/list arguments and if an extra argument is a STAXGlobal (Bug #945541) - Clarified STAXGlobal variable scope in STAX User's Guide (Bug #950525) - Fixed memory leak in the STAX service (Bug #958312) + Added new arguments when starting the STAX Monitor to configure its properties (Feature #909254) - Fixed problem where STAX Monitor was using wrong SCRIPTFILEMACHINE for local if XML Job File machine was not the local machine (Bug #803485) - Fixed problem where "global" variables are not visible to functions defined in one STAXPythonInterpreter when the function is called from a cloned STAXPythonInterpreter (Bug #960415)-------------------------------------------------------------------------------Version 1.5.2.1: 04/07/2004 - Types for function list and map arguments not retained (Bug #931201)-------------------------------------------------------------------------------Version 1.5.2: 04/01/2004 - Synchronize the Process/STAFCmd number and Process key increment methods (Bug #913141) - Fix NullPointerException closing the STAX Monitor (Bug #914357) + Add import of STAFResult class as STAFRC to make it's constant definitions for all the STAF return codes available to STAX jobs (Feature #915820) - Don't return a STAXInvalidStartFunction error when using the TEST option (but not a starting FUNCTION option) for a xml job file that does not contain a <defaultcall> element (Bug #922757) - Fixed STAX Monitor Job Wizard problem when the XML file path contains spaces (Bug #922989) - Fixed problem where RC 7 was not being returned when using the PROCESS KEY option for <process> elements on pre-V2.6.0 STAF machines (Bug #923350)-------------------------------------------------------------------------------Version 1.5.1: 03/03/2004 - Fixed problem displaying job logs from main STAX Monitor window if STAX service name is not STAX (Bug #891895). - Fixed StringIndexOutOfBoundsExceptions in STAX Monitor which could occur monitoring a job if the STAX service name is not STAX (Bug #891970) - Fixed errors deleting temporary files/directory for extension jar files when starting the STAX Monitor (Bug #895302) + Made the STAX Monitor STAX and Event hostname text entry fields larger (Feature #837327) - Fixed STAX Monitor extension "leakage" problem where extension information for other jobs was showing up in the last job monitored (Bug #900523) + Instrumented the STAX servicee's handling of EXECUTE WAIT RETURNRESULT, LIST, and QUERY, SET requests to record diagnostics data to help prepare for the migration to STAF V3.0. The STAX service requires STAF V2.6.0 or later as a result of this change. (Feature #853620) + Updated the STAX <process> element to use the notify key when submitting Process Start commands (Feature #626917)-------------------------------------------------------------------------------Version 1.5.0: 01/26/2004 - Fixed problem in the STAXUtilImportSTAFVars function in STAXUtil.xml where it would fail if only one STAF variable was specified (Bug #816775) - Fixed error where STAX Monitor would not display log entries for levels Debug2/3, Trace 2/3, and User 1/8 (Bug #816882) - Fixed problem where the STAXMonitor's Current Selection tab displayed an extraneous vertical scrollbar (Bug #807198) + Added pyMapEval function (Feature #821394) - Fixed problem where STAX Monitor's Testcase Info table was not displaying testcases with a strict mode and 0 passes/fails (Bug #821471) - Added CLEARLOGS option to STAX QUERY JOB output (Bug #821926) - Fixed RC 7 trying to re-submit STAX job to run via STAX Monitor (Bug #817339) - Fixed problem where the entire STAX Monitor Testcase Information was not being displayed (Bug #825284) - Display stack trace when STAX Monitor extensions throw an InvocationTargetException (Bug #825649) + Added support for logging the elapsed time and/or the number of starts for testcases and provided this info in the STAX Monitor. Also, added support for logging testcase starts and stops in the STAX Job log. Note that the default settings for the STAX service log options are: Clear logs : Disabled Log TC Elapsed Time: Enabled Log TC Num Starts : Enabled Log TC Start/Stop : Disabled These default settings can be changed when registering the STAX service or via the new SET option, or overridden by job when submitting a STAX job for execution. (Feature #795402) - Fixed problem where STAX logs could not be displayed in the STAX Monitor if the service name was not "STAX" (Bug #836579) + Made the STAX Monitor STAX and Event hostname text entry fields larger (Feature #837327)⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?