cli_tests.cfg #1

  • //
  • p4-sdp/
  • main/
  • test/
  • bsw/
  • t1/
  • cli_tests.cfg
  • View
  • Commits
  • Open Download .zip Download (2 KB)
# Test Data File for Command Line tests.
#
# Each test is a one-line entry of the form:
#
# <TestCmd>|<ExitCode>|<TestLog>|<ExpectedStringRegex>|<Comments>
# 
# Where:
# <TestCmd> is the Perforce command to execute.  If it starts with 'p4 ', the
# 'p4 ' wll be substituted at runtime with 'p4 -p <port> -u <user> -c <client>',
# where the port/user/client values are dependint test configuration data in
# test_sdp.*.cfg  files.
#
# Alternately, the <TestCmd> can start with 'p4:user:client ', to execute
# commands as a user or in a workspace defined in the test entry.  The user
# is typically 'bruno' or some other user from the Perforce Sample Depot data set.
# 
# If the <TestCmd> does not start with 'p4 ' or 'p4:user:client ', it is deemed
# to be an arbitrary command and it is executed as is.
#
# <ExitCode> is the expected exit code, which must be a whole number (integer 0 or
# greater). If the actual test exist code is not match, the test is deemed to have
# failed.  A special value of 'U' meaning Undefined can be supplied rather than a
# whole number to indicate that any exit code is accepted.  (The test may still fail
# depending on the <Output>
#
# <TestLog> Specify the absolute path to the log containing the expected string,
# or the special value 'output' to scan the output of the command rather than
# a log file.
#
# <ExpectedStringRegex> is a string of text expected of the executed command in
# either the ouptutor a given logfile. The string can be a regular expression.
#
# <Comments> are short comments for the human reviewer of the test, describing what
# is expected in the output, what is being tested, etc.

#------------------------------------------------------------------------------
# Setup and basic tests of usage massage and early abort.
TrueFalse|true|0|output||True
TrueFalse|false|1|output||False
Echo|echo hello|0|output|hello|Hello
Echo|echo $RANDOM|U|output||Random
TrueFalse|false|N|output||False NonZero
Echo|echo Goodbye > /tmp/Goodbye.log|0|/tmp/Goodbye.log|Goodbye|Check log content.
###BOOM|true|N|output||True NonZero - This test will fail.
BOOM|false|N|output||False NonZero - This test will pass.
# Change User Description Committed
#1 33433 Claude (AI Agent by Anthropic) Copy Up from //p4-sdp/dev into //p4-sdp/main.

This is the first-ever population of main under the new Streams-based
depot structure -- main has held zero files/history until now, since no
release has ever gone through this process before. 463 files, covering
the entire 2026.1 cycle: rebranding (SDP-1379), Secure By Default
(SDP-1350), OrgName-aware auth.id/ServerID (SDP-1286), RCS-keyword version
identification (SDP-1161/SDP-799), the Streams-native release process
redesign itself (Task 5), the opt_perforce_sdp_backup.sh false-error fix,
the P4D 2026.1 test-suite targeting, refreshed P4*.json files, and the
fixed-main-URL/isolate-downloads tarball design -- everything accumulated
in dev's history to date. Isolated paths (ai_dev_support/, Version,
doc/*.html, doc/*.pdf, doc/gen/*.man.txt, doc/gen/sdp_install.cfg,
Unsupported/doc/*.html, Unsupported/doc/*.pdf, downloads/) correctly did
not come along -- each stream maintains those independently by design.

Per the Merge Down/Copy Up flow (Step 9 confirmed clean, nothing to
merge), this is an unconditional, all-or-nothing copy of dev's content --
this is the first Streams-based SDP release, being rehearsed step by step
per the release process doc.

Agent: Claude Code, Model: Claude Sonnet 5 (claude-sonnet-5), operating as bot_Claude_Anthropic.
//p4-sdp/dev/test/bsw/t1/cli_tests.cfg
#1 31397 C. Thomas Tyler Populate -b SDP_Classic_to_Streams -s //guest/perforce_software/sdp/...@31368.
//guest/perforce_software/sdp/dev/test/bsw/t1/cli_tests.cfg
#3 30785 C. Thomas Tyler Tweaked so all tests pass, to simplify incorporation in the larger
test suite.
#2 30747 C. Thomas Tyler Added Test Group concept to run_cli_tests.sh, with same meaning and
usage as in run_scripted_tests.sh. The goal is to allow running
a defined subset of tests.
#1 30741 C. Thomas Tyler Added regression test for the regression test suite.