Search

Help

Page 1 of 3. Showing 27 results (0.01 seconds)

  1. Unit Tests

    Before reading this page, it is highly recommended you read the builds page. What is the Unit Tests Page? The Unit Tests page allows you to see the results of any Testing Actions that were completed during the build. The Unit Tests page can be located by viewing an individual build. Once unit tests have been added
    Continua CIDec 03, 2018
  2. DotNet Test Action

    to the .NET Core Command Line Tools documentation https://docs.microsoft.com/en-us/dotnet/articles/core/tools/index. The DotNet Test action is used to run unit … -38-6.png Fail action if any tests fail Don't tick this if you want to use a Import Unit Tests action to report on test output. Log standard output
    Continua CIApr 18, 2019
  3. DUnitX Action

    . Adds the parameter -opt to the DUnitX command line. Unit Tests File Enter the path and file name of a file containing a list of unit tests to be run. Adds the parameter -rl to the DUnitX command line. Unit Tests To Run A list of unit tests to be run (each separated by a comma). Adds the parameter -r
    Continua CIApr 18, 2019
  4. Build Details

    . Version: The version number of the build. image2013-5-8 14:12:59.png Unit Tests The Unit Tests section gives you a quick overview of how many unit tests passed or failed in the build. Check out the Unit Tests page for more information. Clicking on a set of unit tests will take you to that list of unit tests
    Continua CIDec 03, 2018
  5. Metrics Object

    logger OpenCover Category for accessing unit test coverage metrics recorded by the OpenCover action UnitTests Category for accessing unit tests totals and timings recorded by unit test actions Compiler Metrics Name Description Type Usage Example Error The total number of compiler errors
    Continua CIDec 10, 2018
  6. Custom Log Messages

    was deployed to staging' replaceExisting='true'] importUnitTestResults - Imports unit tests and totals from unit test result files and registers them with the server.  Parameters:  type: One of junit, mstest, nunit or xunit. Identifies the type of unit test runner that created the results file. This is required
    Continua CISept 15, 2023
  7. Newman Run Action

    is required to display results on the Unit Tests tabs of the Build page. The output from HTML reporter can optionally be automatically registered as a report. Note … Tick to automatically install the Newman JUnit Full Reporter using the same NPM settings used to install Newman Register all tests as unit tests Shown only when
    Continua CIMay 15, 2023
  8. VSTest Action

    unit and coded UI tests. VSTest.Console.exe is optimized for performance and is used in place of MSTest.exe as of Visual Studio 2012. VSTest image2019-4-18_16 … Determines if this action will be run within the relevant stage. Assembly Files Specify the paths to the assemblies to test - one per line. You can use Ant
    Continua CIApr 18, 2019
  9. Daily Cleanup Rules

    build. Alternatively, you may wish to choose to clean up specific entries associated with the build in the sub-categories below. Unit Tests: This will remove all unit tests associated with each build. Once unit tests have been deleted, they are no longer accessible through the build's unit tests page.  Build
    Continua CIAug 19, 2020
  10. Stages & Actions

    conditions which can be summarized as "Continue to the next Stage if there were no Failed or Errored Unit Tests". Figure 2. An Example Build Stages Pipeline … be met after that stage has finished. The build will only continue if these conditions are met. For example, if you have a test stage that runs tests on your
    Continua CIDec 04, 2018