Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -606,12 +606,6 @@ Read more about Microsoft Testing Platform telemetry: https://aka.ms/testingplat
<data name="Aborted" xml:space="preserve">
<value>Aborted</value>
</data>
<data name="Actual" xml:space="preserve">
<value>Actual</value>
</data>
<data name="CancelledLowercase" xml:space="preserve">
<value>canceled</value>
</data>
<data name="CancellingTestSession" xml:space="preserve">
<value>Canceling the test session...</value>
</data>
Expand All @@ -631,35 +625,15 @@ Read more about Microsoft Testing Platform telemetry: https://aka.ms/testingplat
<value>Diagnostic file (level '{0}' with sync flush): {1}</value>
<comment>{0} is the diagnostic log level, such as verbose. {1} is the path to the diagnostic log file.</comment>
</data>
<data name="Expected" xml:space="preserve">
<value>Expected</value>
</data>
<data name="Failed" xml:space="preserve">
<value>Failed</value>
</data>
<data name="FailedLowercase" xml:space="preserve">
<value>failed</value>
</data>
<data name="ForTest" xml:space="preserve">
<value>For test</value>
<comment>is followed by test name</comment>
</data>
<data name="InProcessArtifactsProduced" xml:space="preserve">
<value>In process file artifacts produced:</value>
</data>
<data name="MinimumExpectedTestsPolicyViolation" xml:space="preserve">
<value>Minimum expected tests policy violation, tests ran {0}, minimum expected {1}</value>
<comment>{0} is the number of tests that ran. {1} is the minimum expected number of tests.</comment>
</data>
<data name="OutOfProcessArtifactsProduced" xml:space="preserve">
<value>Out of process file artifacts produced:</value>
</data>
<data name="Passed" xml:space="preserve">
<value>Passed</value>
</data>
Comment thread
Evangelink marked this conversation as resolved.
<data name="PassedLowercase" xml:space="preserve">
<value>passed</value>
</data>
<data name="Skipped" xml:space="preserve">
<value>Skipped</value>
</data>
Expand All @@ -678,13 +652,6 @@ Read more about Microsoft Testing Platform telemetry: https://aka.ms/testingplat
<data name="ZeroTestsRan" xml:space="preserve">
<value>Zero tests ran</value>
</data>
<data name="ConsoleIsAlreadyInBatchingMode" xml:space="preserve">
<value>Console is already in batching mode.</value>
<comment>Exception that is thrown when console is already collecting input into a batch (into a string builder), and code asks to enable batching mode again.</comment>
</data>
<data name="DurationLowercase" xml:space="preserve">
<value>duration</value>
</data>
<data name="FailedWithErrors" xml:space="preserve">
<value>failed with {0} error(s)</value>
<comment>{0} is the number of errors.</comment>
Expand All @@ -700,95 +667,14 @@ Read more about Microsoft Testing Platform telemetry: https://aka.ms/testingplat
<data name="RunningTestsFrom" xml:space="preserve">
<value>Running tests from</value>
</data>
<data name="TestRunSummary" xml:space="preserve">
<value>Test run summary:</value>
</data>
<data name="FromFile" xml:space="preserve">
<value>from</value>
<comment>from followed by a file name to point to the file from which test is originating</comment>
</data>
<data name="StackFrameAt" xml:space="preserve">
<value>at</value>
<comment>at that is used for a stack frame location in a stack trace, is followed by a class and method name</comment>
</data>
<data name="StackFrameIn" xml:space="preserve">
<value>in</value>
<comment>in that is used in stack frame it is followed by file name</comment>
</data>
<data name="TerminalNoAnsiOptionDescription" xml:space="preserve">
<value>Disable outputting ANSI escape characters to screen.</value>
</data>
<data name="TerminalAnsiOptionDescription" xml:space="preserve">
<value>Control whether ANSI escape characters are emitted.
Valid values are 'auto' (default), 'on' (also accepts 'true', 'enable', '1') or 'off' (also accepts 'false', 'disable', '0').
'on' forces ANSI escape codes (including cursor movement) even when stdout is redirected; pair it with --progress off if you only want colors.
When both --ansi and --no-ansi are provided, --ansi wins.</value>
<comment>{Locked="auto"}{Locked="on"}{Locked="true"}{Locked="enable"}{Locked="1"}{Locked="off"}{Locked="false"}{Locked="disable"}{Locked="0"}{Locked="--progress off"}{Locked="--ansi"}{Locked="--no-ansi"}</comment>
</data>
<data name="TerminalAnsiOptionInvalidArgument" xml:space="preserve">
<value>--ansi expects a single parameter with value 'auto', 'on' (or 'true', 'enable', '1') or 'off' (or 'false', 'disable', '0').</value>
<comment>{Locked="--ansi"}{Locked="auto"}{Locked="on"}{Locked="true"}{Locked="enable"}{Locked="1"}{Locked="off"}{Locked="false"}{Locked="disable"}{Locked="0"}</comment>
</data>
<data name="TerminalNoProgressOptionDescription" xml:space="preserve">
<value>[Deprecated, use '--progress off' instead] Disable reporting progress to screen.</value>
<comment>{Locked="--progress off"}</comment>
</data>
<data name="TerminalProgressOptionDescription" xml:space="preserve">
<value>Control whether progress is reported to screen.
Valid values are 'auto' (default), 'on' (also accepts 'true', 'enable', '1') or 'off' (also accepts 'false', 'disable', '0').
'auto' shows progress unless the terminal cannot update in place (for example with --no-ansi or in CI).
This option takes precedence over the deprecated --no-progress flag.</value>
<comment>{Locked="auto"}{Locked="on"}{Locked="true"}{Locked="enable"}{Locked="1"}{Locked="off"}{Locked="false"}{Locked="disable"}{Locked="0"}{Locked="--no-ansi"}{Locked="--no-progress"}</comment>
</data>
<data name="TerminalProgressOptionInvalidArgument" xml:space="preserve">
<value>--progress expects a single parameter with value 'auto', 'on' (or 'true', 'enable', '1') or 'off' (or 'false', 'disable', '0').</value>
<comment>{Locked="--progress"}{Locked="auto"}{Locked="on"}{Locked="true"}{Locked="enable"}{Locked="1"}{Locked="off"}{Locked="false"}{Locked="disable"}{Locked="0"}</comment>
</data>
<data name="TerminalNoProgressDeprecatedWarning" xml:space="preserve">
<value>warning: --no-progress is deprecated; use --progress off instead.</value>
<comment>{Locked="--no-progress"}{Locked="--progress off"}</comment>
</data>
<data name="TerminalProgressHeartbeat" xml:space="preserve">
<value>running... {0} completed, {1} failed</value>
<comment>Heartbeat line emitted on non-cursor terminals when the run goes silent. {0} is the number of completed tests, {1} is the number of failed tests.</comment>
</data>
<data name="TerminalProgressHeartbeatActiveSuffix" xml:space="preserve">
<value> | active: {0}</value>
<comment>Suffix appended to the heartbeat line naming the currently active test. {0} is the active test name.</comment>
</data>
<data name="TerminalProgressSlowTest" xml:space="preserve">
<value>[slow] still running after {0}: {1}</value>
<comment>Line emitted on non-cursor terminals when a single test runs longer than the slow-test threshold. {0} is the elapsed duration, {1} is the test description. {Locked="[slow]"}</comment>
</data>
<data name="TerminalTestReporterDescription" xml:space="preserve">
<value>Writes test results to terminal.</value>
</data>
<data name="TerminalTestReporterDisplayName" xml:space="preserve">
<value>Terminal test reporter</value>
</data>
<data name="TerminalOutputOptionDescription" xml:space="preserve">
<value>Output verbosity when reporting tests.
Valid values are 'Normal', 'Detailed'. Default is 'Normal'.</value>
<comment>{Locked="Normal"}{Locked="Detailed"}</comment>
</data>
<data name="TerminalOutputOptionInvalidArgument" xml:space="preserve">
<value>--output expects a single parameter with value 'Normal' or 'Detailed'.</value>
<comment>{Locked="--output"}{Locked="Normal"}{Locked="Detailed"}</comment>
</data>
<data name="TerminalShowStdoutOptionDescription" xml:space="preserve">
<value>Determines when to show captured standard output of a test.
Valid values are 'All', 'Failed', 'None'. Default is 'All' (or 'Failed' when an LLM/AI agent environment is detected).</value>
<comment>{Locked="All"}{Locked="Failed"}{Locked="None"}</comment>
</data>
<data name="TerminalShowStderrOptionDescription" xml:space="preserve">
<value>Determines when to show captured error output of a test.
Valid values are 'All', 'Failed', 'None'. Default is 'All' (or 'Failed' when an LLM/AI agent environment is detected).</value>
<comment>{Locked="All"}{Locked="Failed"}{Locked="None"}</comment>
</data>
<data name="TerminalShowOutputOptionInvalidArgument" xml:space="preserve">
<value>--show-stdout and --show-stderr expect a single parameter with value 'All', 'Failed', or 'None'.</value>
<comment>{Locked="--show-stdout"}{Locked="--show-stderr"}{Locked="All"}{Locked="Failed"}{Locked="None"}</comment>
</data>
<data name="PlatformCommandLineTimeoutArgumentErrorMessage" xml:space="preserve">
<value>'timeout' option should have one argument as a time value with an explicit unit suffix and a positive numeric value within the supported range (up to ~49.7 days). Accepted suffixes are 'ms'/'mil(s)'/'millisecond(s)', 's'/'sec(s)'/'second(s)', 'm'/'min(s)'/'minute(s)', 'h'/'hour(s)', and 'd'/'day(s)', e.g. '500ms', '5400s', '90m', '1.5h', '1d'.</value>
<comment>{Locked="timeout"}{Locked="ms"}{Locked="mil(s)"}{Locked="millisecond(s)"}{Locked="s"}{Locked="sec(s)"}{Locked="second(s)"}{Locked="m"}{Locked="min(s)"}{Locked="minute(s)"}{Locked="h"}{Locked="hour(s)"}{Locked="d"}{Locked="day(s)"}{Locked="500ms"}{Locked="5400s"}{Locked="90m"}{Locked="1.5h"}{Locked="1d"}</comment>
Expand All @@ -813,12 +699,6 @@ Takes one argument as a time value with an explicit unit suffix. Accepted suffix
<value>Expected --client-port when jsonRpc protocol is used.</value>
<comment>{Locked="--client-port"}{Locked="jsonRpc"}</comment>
</data>
<data name="StandardError" xml:space="preserve">
<value>Error output</value>
</data>
<data name="StandardOutput" xml:space="preserve">
<value>Standard output</value>
</data>
<data name="DiscoveringTestsFrom" xml:space="preserve">
<value>Discovering tests from</value>
</data>
Expand All @@ -830,10 +710,6 @@ Takes one argument as a time value with an explicit unit suffix. Accepted suffix
<value>Discovered {0} test(s) in assembly</value>
<comment>{0} is the number of discovered tests. The sentence is followed by the assembly path.</comment>
</data>
<data name="TestDiscoverySummarySingular" xml:space="preserve">
<value>Test discovery summary: found {0} test(s)</value>
<comment>{0} is the number of discovered tests.</comment>
</data>
<data name="ExitCode" xml:space="preserve">
<value>Exit code</value>
</data>
Expand Down
Loading
Loading