public class DTestStepProcessor extends TestStepProcessor
Modifier and Type | Field and Description |
---|---|
protected DTestRecordHelper |
droiddata |
protected java.util.ArrayList |
processors |
protected java.util.Properties |
props |
cfBreakpointsOn, DEFAULT_TEST_STEP_CLASSNAME, DEFAULT_TEST_STEP_PREFIX
breakpointsOn, CASE_INSENSITIVE_FLAG, CASEINSENSITIVE_FLAG, clearProxiesAlways, commandLineBreakpoint, customStr, customText, DEBUG_MESSAGE, debugStr, debugText, DEFAULT_CUSTOM_PROCESSOR_PACKAGE, DEFAULT_CUSTOM_PROCESSOR_SUBPACKAGE, DEFAULT_PROCESSOR_PACKAGE, FAILED_MESSAGE, FAILED_OK_MESSAGE, failedStr, failedText, FAILURE_DETAIL, GENERIC_MESSAGE, genericStr, genericText, LINE_FAILURE_4, log, myBreakpointsOn, otherStr, otherText, PARAM_SIZE_1, PARAM_SIZE_2, PARAM_SIZE_3, PARAM_SIZE_4, params, PASSED_MESSAGE, passedStr, passedText, PRE_TXT_SUCCESS_4, PRE_TXT_SUCCESS_5, processorConfigSet, processorMap, recordProcessed, RECTYPE_DRIVER_COMMAND, RECTYPE_DRIVER_COMMAND_F, RECTYPE_DRIVER_COMMAND_W, RECTYPE_TEST_STEP, RECTYPE_TEST_STEP_F, RECTYPE_TEST_STEP_W, RFSMCache, RFSMOnly, RFT_FIND_SEARCH_MODE_ALGORITHM, RFT_FIND_SEARCH_MODE_CACHE, SAFS_CLEARPROXIESALWAYS_ITEM, SAFS_COMMANDLINEBREAKPOINT_ITEM, SAFS_COMMANDLINEBREAKPOINT_VARIABLE, SAFS_PARAMS_FILE, SAFS_RESBUN_NAME, SAFS_SECSWAITFORCOMPONENT_ITEM, SAFS_SECSWAITFORCOMPONENT_VARIABLE, SAFS_SECSWAITFORWINDOW_ITEM, SAFS_SECSWAITFORWINDOW_VARIABLE, SAFS_TESTDOMAINS_ITEM, SAFS_TESTDOMAINS_VARIABLE, secsWaitForComponent, secsWaitForWindow, SENT_MSG_3, testDomains, testRecordData, testrecordStackable, TXT_FAILURE_1, TXT_FAILURE_2, TXT_FAILURE_3, TXT_FAILURE_4, TXT_FAILURE_5, TXT_SUCCESS_1, TXT_SUCCESS_2, TXT_SUCCESS_2a, TXT_SUCCESS_3, TXT_SUCCESS_3a, TXT_SUCCESS_4, TXT_SUCCESS_5, unexpectedAlertBehaviour, WARNING_MESSAGE, WARNING_OK_MESSAGE, warningStr, warningText
Constructor and Description |
---|
DTestStepProcessor() |
Modifier and Type | Method and Description |
---|---|
protected java.util.Collection |
interpretFields()
Calls the default processing of interpretFields and then prepares the
droiddata (testRecordData) with the initial KeywordProperties of:
|
void |
process()
Purpose: process: process the testRecordData |
void |
setLogUtilities(LogUtilities _log) |
void |
setTestRecordData(TestRecordHelper data) |
checkMyBreakpoints, componentFailureMessage, componentWarningMessage, getComponentProcClassName, getCustomProcClassNames, getProcClassNames, getWinAndCompGUIObjects, instantiateComponentFunction, isCFBreakpointsOn, isSupportedRecordType, postProcess, setActiveWindow, setCFBreakpointsOn, waitForObject, waitForObjectAndCheck
activateBreakpoint, checkBreakpoints, deduceBenchFile, deduceDiffFile, deduceProjectFile, deduceTestFile, delay, distributeConfigInformation, getAbsolutFileName, getAlternateParams, getAppMapItem, getChainedProcessor, getClassInstance, getClearProxiesAlways, getCustomProcInstancePath, getLogUtilities, getParams, getProcInstance, getProcInstancePath, getRequiredField, getSecsWaitForComponent, getSecsWaitForWindow, getStandardErrorMessage, getTestRecordData, getUnexpectedAlertBehaviour, getVariable, hasChainedProcessor, initProcessorAndProcess, instanceProcessorAndProcess, isBreakpointsOn, isComponentFunctionRecord, isDriverCommandRecord, isEngineCommandRecord, isMyBreakpointsOn, isRecordProcessed, isRFSMCache, isRFSMOnly, issueActionFailure, issueActionOnXFailure, issueErrorPerformingAction, issueErrorPerformingActionOnX, issueErrorPerformingActionUsing, issueInputRecordFailure, issueInputRecordFailure, issuePassedSuccess, logFailureMessage, normalizeTestFileName, paramsFailedMsg, paramsFailedMsg, popTestRecord, processCustomProcessor, processSubclassProcessor, pushTestRecord, setAtEndOfProcess, setBreakpointsOn, setChainedProcessor, setClearProxiesAlways, setCommandLineBreakpoint, setCustomProcInstancePath, setMyBreakpointsOn, setParams, setProcInstance, setProcInstancePath, setRecordProcessed, setRFSMCache, setRFSMOnly, setSecsWaitForComponent, setSecsWaitForWindow, setTestDomains, setUnexpectedAlertBehaviour, setVariable, standardFailureMessage, substituteVariable, validateParamSize, validProcessorClassName
protected DTestRecordHelper droiddata
protected java.util.Properties props
protected java.util.ArrayList processors
public void setLogUtilities(LogUtilities _log)
setLogUtilities
in class Processor
public void setTestRecordData(TestRecordHelper data)
setTestRecordData
in class Processor
protected java.util.Collection interpretFields() throws SAFSException
Keyword implementations will need to add to these properties:
interpretFields
in class TestStepProcessor
SAFSException
public void process()
At this point the Driver has determined we are dealing with a Test Record. A Test Record is one acting on a window or a component within a window.
Field #1: The TEST record type (T).
Subsequent fields would be as follows (with a separator between each field):
Field: #2 #3 #4 #5 - N
============== ============== ======== ===============
WINDOWNAME, COMPONENTNAME, ACTION, [PARAMETER(S),]
WINDOWNAME is the name given the window in the appmap that you intend to have focus for this test step.
COMPONENTNAME is the name of the component within that window you intend to perform some function or test on. If it is the window itself then the COMPONENTNAME should be the same as the WINDOWNAME.
ACTION is the command or test you wish to perform. Different types of components support different types of actions. Almost all support some versions of VERIFY actions. Pushbuttons can be CLICKed etc... Consult each Component's TYPE or CLASS documentation for the actions available for the component.
PARAMETER(s) are the additional fields needed based upon the action to be completed. Each action can have its own unique set of parameters. Some actions may take no parameters at all. Consult the component's TYPE or CLASS documentation for the parameters needed for a given action.
Although the separator used in the example above is a comma, any separator can be used as long as it is specified at the time the file is provided or in subsequent command lines which might change the separator in use.
NOTE:
A user or developer would not normally call this routine. This
routine is intended to be called from the StepDriver routine as
deemed necessary by the input records of the data table provided to
the StepDriver routine. The internals of this routine and the declaration
and parameters are all subject to change as necessary.
Side Effects: Processor.testRecordData
statusCode and statusInfo are set
based on the result of the processing
State Read: Processor.testRecordData
process
in class TestStepProcessor
Copyright © SAS Institute. All Rights Reserved.