<?xml version="1.0" encoding="utf-8"?>
<root>
  <!-- 
    Microsoft ResX Schema 
    
    Version 2.0
    
    The primary goals of this format is to allow a simple XML format 
    that is mostly human readable. The generation and parsing of the 
    various data types are done through the TypeConverter classes 
    associated with the data types.
    
    Example:
    
    ... ado.net/XML headers & schema ...
    <resheader name="resmimetype">text/microsoft-resx</resheader>
    <resheader name="version">2.0</resheader>
    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
    <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
        <value>[base64 mime encoded serialized .NET Framework object]</value>
    </data>
    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
        <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
        <comment>This is a comment</comment>
    </data>
                
    There are any number of "resheader" rows that contain simple 
    name/value pairs.
    
    Each data row contains a name, and value. The row also contains a 
    type or mimetype. Type corresponds to a .NET class that support 
    text/value conversion through the TypeConverter architecture. 
    Classes that don't support this are serialized and stored with the 
    mimetype set.
    
    The mimetype is used for serialized objects, and tells the 
    ResXResourceReader how to depersist the object. This is currently not 
    extensible. For a given mimetype the value must be set accordingly:
    
    Note - application/x-microsoft.net.object.binary.base64 is the format 
    that the ResXResourceWriter will generate, however the reader can 
    read any of the formats listed below.
    
    mimetype: application/x-microsoft.net.object.binary.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
            : and then encoded with base64 encoding.
    
    mimetype: application/x-microsoft.net.object.soap.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Soap.SoapFormatter
            : and then encoded with base64 encoding.

    mimetype: application/x-microsoft.net.object.bytearray.base64
    value   : The object must be serialized into a byte array 
            : using a System.ComponentModel.TypeConverter
            : and then encoded with base64 encoding.
    -->
  <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
    <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
    <xsd:element name="root" msdata:IsDataSet="true">
      <xsd:complexType>
        <xsd:choice maxOccurs="unbounded">
          <xsd:element name="metadata">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" />
              </xsd:sequence>
              <xsd:attribute name="name" use="required" type="xsd:string" />
              <xsd:attribute name="type" type="xsd:string" />
              <xsd:attribute name="mimetype" type="xsd:string" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="assembly">
            <xsd:complexType>
              <xsd:attribute name="alias" type="xsd:string" />
              <xsd:attribute name="name" type="xsd:string" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="data">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
              <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
              <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="resheader">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" />
            </xsd:complexType>
          </xsd:element>
        </xsd:choice>
      </xsd:complexType>
    </xsd:element>
  </xsd:schema>
  <resheader name="resmimetype">
    <value>text/microsoft-resx</value>
  </resheader>
  <resheader name="version">
    <value>2.0</value>
  </resheader>
  <resheader name="reader">
    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <resheader name="writer">
    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <data name="FailedToCreateRetryDirectoryBecauseOfCollision" xml:space="preserve">
    <value>Failed to create retries directory due to collisions in '{0}' despite re-trying.</value>
    <comment>'{0}' is the directory where collisions happen</comment>
  </data>
  <data name="FailureThresholdPolicy" xml:space="preserve">
    <value>Failure threshold policy is enabled, failed tests will not be restarted.</value>
  </data>
  <data name="FailureThresholdPolicyMaxCount" xml:space="preserve">
    <value>Maximum failed tests threshold is {0} and {1} tests failed</value>
    <comment>{0} is the maximum failed tests threshold. {1} is the failed tests count.</comment>
  </data>
  <data name="FailureThresholdPolicyMaxPercentage" xml:space="preserve">
    <value>Percentage failed threshold is {0}% and {1}% tests failed ({2}/{3})</value>
    <comment>{0} is the maximum failed tests percentage threshold. {1} is the actual failed tests percentage. {2} is the failed tests count. {3} is the total tests count.</comment>
  </data>
  <data name="RetryArtifactsMoved" xml:space="preserve">
    <value>Retry: moved {0} result file(s) to '{1}'</value>
    <comment>{0} is the number of files moved. {1} is the destination result directory.</comment>
  </data>
  <data name="RetryAttemptFailedWillRetry" xml:space="preserve">
    <value>Retry: attempt {0}/{1} failed - {2} failing test(s), retrying</value>
    <comment>{0} is the current attempt number. {1} is the total number of attempts. {2} is the number of failing tests in this attempt.</comment>
  </data>
  <data name="RetryWaitingBeforeNextAttempt" xml:space="preserve">
    <value>Retry: waiting {0} before attempt {1}/{2}</value>
    <comment>{0} is the delay (e.g. '1s'). {1} is the next attempt number. {2} is the total number of attempts.</comment>
  </data>
  <data name="RetrySummaryPassed" xml:space="preserve">
    <value>Retry summary: Passed! after {0}/{1} attempts</value>
    <comment>{0} is the number of attempts used. {1} is the maximum number of attempts. Keep 'Retry summary:' and 'Passed!' parallel to the platform 'Test run summary: Passed!' wording.</comment>
  </data>
  <data name="RetrySummaryPassedNoRetry" xml:space="preserve">
    <value>Retry summary: Passed! on the first attempt (no retries needed)</value>
    <comment>Keep 'Retry summary:' and 'Passed!' parallel to the platform 'Test run summary: Passed!' wording.</comment>
  </data>
  <data name="RetrySummaryFailed" xml:space="preserve">
    <value>Retry summary: Failed! after {0}/{1} attempts</value>
    <comment>{0} is the number of attempts used. {1} is the maximum number of attempts. Keep 'Retry summary:' and 'Failed!' parallel to the platform 'Test run summary: Failed!' wording.</comment>
  </data>
  <data name="RetrySummaryFailedStoppedEarly" xml:space="preserve">
    <value>Retry summary: Failed! after {0} attempt(s) (retrying stopped early)</value>
    <comment>{0} is the number of attempts that actually ran. Used when retrying was cut short by the failure threshold policy or by an attempt exiting unexpectedly, so the maximum attempt count would be misleading. Keep 'Retry summary:' and 'Failed!' parallel to the platform 'Test run summary: Failed!' wording. The '(s)' suffix follows the existing convention used elsewhere in this extension for counts that may be one.</comment>
  </data>
  <data name="RetrySummaryFailedLine" xml:space="preserve">
    <value>  failed: {0}</value>
    <comment>{0} is the number of tests still failing after the final attempt. Two leading spaces and the lowercase 'failed:' label mirror the platform run summary.</comment>
  </data>
  <data name="RetrySummaryFlakyLine" xml:space="preserve">
    <value>  flaky: {0} (passed after retry)</value>
    <comment>{0} is the number of tests that failed at least once but eventually passed. Two leading spaces mirror the platform run summary. The parenthetical is important: it states that these tests are already included in the 'succeeded' count rather than forming a fourth outcome category alongside failed/succeeded/skipped.</comment>
  </data>
  <data name="RetrySummaryFlakyTestsHeader" xml:space="preserve">
    <value>Flaky tests:</value>
    <comment>Header of the section that lists, by name, the tests which failed at least once but eventually passed.</comment>
  </data>
  <data name="RetrySummaryFlakyTestLine" xml:space="preserve">
    <value>  {0} (failed -&gt; passed)</value>
    <comment>{0} is the display name of a flaky test. The arrow reads left (first outcome) to right (final outcome). Two leading spaces indent the entry under the 'Flaky tests:' header.</comment>
  </data>
  <data name="RetrySummaryTotalLine" xml:space="preserve">
    <value>  total: {0}</value>
    <comment>{0} is the total number of tests in the suite. Two leading spaces and the lowercase 'total:' label mirror the platform run summary.</comment>
  </data>
  <data name="RetrySummarySucceededLine" xml:space="preserve">
    <value>  succeeded: {0}</value>
    <comment>{0} is the number of tests that ended up passing, counting those rescued by a retry. Two leading spaces and the lowercase 'succeeded:' label mirror the platform run summary.</comment>
  </data>
  <data name="RetrySummarySkippedLine" xml:space="preserve">
    <value>  skipped: {0}</value>
    <comment>{0} is the number of skipped tests. Two leading spaces and the lowercase 'skipped:' label mirror the platform run summary.</comment>
  </data>
  <data name="RetrySummaryRetriedLine" xml:space="preserve">
    <value>  retried: {0} test(s), {1} extra run(s)</value>
    <comment>{0} is the number of distinct tests that were re-run. {1} is the number of extra executions those retries cost. Two leading spaces and the lowercase 'retried:' label mirror the platform run summary. The '(s)' suffix follows the existing convention used elsewhere in this extension for counts that may be one.</comment>
  </data>
  <data name="RetrySummaryDurationLine" xml:space="preserve">
    <value>  duration: {0}</value>
    <comment>{0} is the total retry orchestration duration. Two leading spaces and the lowercase 'duration:' label mirror the platform run summary.</comment>
  </data>
  <data name="RetryFailedTestsCannotStartProcessErrorMessage" xml:space="preserve">
    <value>Failed to start process '{0}'</value>
    <comment>{0} is the process file path.</comment>
  </data>
  <data name="RetryFailedTestsExtensionDescription" xml:space="preserve">
    <value>Retry failed tests feature allows to restart test execution upon failure.</value>
  </data>
  <data name="RetryFailedTestsExtensionDisplayName" xml:space="preserve">
    <value>Retry failed tests</value>
  </data>
  <data name="RetryExtensionNotSupportedOnBrowserErrorMessage" xml:space="preserve">
    <value>The retry extension is not supported on browser platform. Browser-based tests cannot be retried due to platform limitations.</value>
  </data>
  <data name="RetryFailedTestsMaxPercentageOptionDescription" xml:space="preserve">
    <value>Disable retry mechanism if the percentage of failed tests is greater than the specified value</value>
    <comment>Do not localize option name {Locked="--retry-failed-tests-max-percentage"}.</comment>
  </data>
  <data name="RetryFailedTestsMaxTestsOptionDescription" xml:space="preserve">
    <value>Disable retry mechanism if the number of failed tests is greater than the specified value</value>
    <comment>Do not localize option name {Locked="--retry-failed-tests-max-tests"}.</comment>
  </data>
  <data name="RetryFailedTestsNotSupportedInHotReloadErrorMessage" xml:space="preserve">
    <value>Retry failed tests feature is not supported in hot reload mode</value>
  </data>
  <data name="RetryFailedTestsNotSupportedInServerModeErrorMessage" xml:space="preserve">
    <value>Retry failed tests feature is not supported in server mode</value>
  </data>
  <data name="RetryFailedTestsDelayOptionDescription" xml:space="preserve">
    <value>Add a delay between retries. The delay is expressed as a time value, e.g. 200, 500ms, 1s, 2.5m, 1h, 1d. Default unit is milliseconds.</value>
    <comment>Do not localize option name {Locked="--retry-failed-tests-delay"} or time examples {Locked="200"}{Locked="500ms"}{Locked="1s"}{Locked="2.5m"}{Locked="1h"}{Locked="1d"}.</comment>
  </data>
  <data name="RetryFailedTestsDelayOptionInvalidArgument" xml:space="preserve">
    <value>Option '--retry-failed-tests-delay' requires a valid time span value that is non-negative and no greater than 2147483647ms (~24.20:31:23.647) (e.g. 200, 500ms, 1s, 2.5m, 1h, 1d)</value>
    <comment>Do not localize option name {Locked="--retry-failed-tests-delay"} or time examples {Locked="2147483647ms"}{Locked="200"}{Locked="500ms"}{Locked="1s"}{Locked="2.5m"}{Locked="1h"}{Locked="1d"}.</comment>
  </data>
  <data name="RetryFailedTestsOptionDescription" xml:space="preserve">
    <value>Retry failed tests the given number of times</value>
    <comment>Do not localize option name {Locked="--retry-failed-tests"}.</comment>
  </data>
  <data name="RetryFailedTestsOptionIsMissingErrorMessage" xml:space="preserve">
    <value>Option '{0}' requires option '{1}' to be specified</value>
    <comment>{0} is the option name that was specified. {1} is the required option name.</comment>
  </data>
  <data name="RetryFailedTestsOptionNonNegativeIntegerArgumentErrorMessage" xml:space="preserve">
    <value>Option '{0}' expects a non-negative integer argument</value>
    <comment>{0} is the option name.</comment>
  </data>
  <data name="RetryFailedTestsMaxPercentageOptionIntegerBetween0And100ArgumentErrorMessage" xml:space="preserve">
    <value>Option '{0}' expects an integer argument between 0 and 100</value>
    <comment>{0} is the option name.</comment>
  </data>
  <data name="RetryFailedTestsPercentageAndCountCannotBeMixedErrorMessage" xml:space="preserve">
    <value>Options '{0}' and '{1}' cannot be used together</value>
    <comment>{0} is the first option name. {1} is the second option name.</comment>
  </data>
  <data name="TestHostProcessExitedBeforeRetryCouldConnect" xml:space="preserve">
    <value>Test host process exited before the retry service could connect to it. Exit code: {0}</value>
    <comment>{0} is the test host process exit code.</comment>
  </data>
  <data name="TestSuiteFailedWithWrongExitCode" xml:space="preserve">
    <value>Test suite failed with and exit code different that 2 (failed tests). Failure related to an unexpected condition. Exit code '{0}'</value>
    <comment>{0} is the exit code.</comment>
  </data>
</root>