945 Update trusted-context testscripts for current cldriver messages and also allow running from remote #951
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Testcases changed files (3).
Allow trusted-context testcases to run on a hostname that is different from that of the Db2-server (i.e allow to run from remote). Allow the default hostname allowed in the trusted context to be local hostname, but additionally allow the config.py to specify the IP-address of the trusted-context IP-address to support the scenario of the Db2-server being unable to resolve the remote hostname (so can instead use the remote IP-address).
Updated the EXPECTED RESPONSE for one specific SQLCODE to reflect the current (11.5.9) english-language revised-message-text issued by clidriver, this allows the trusted-context testcases to pass , at least when tested on Db2-LUW. ( I lack any i-series or z/os environment access to test against those platforms).
Notice that no additional python modules are required other than those already used by the python-ibmdb-testcases