I am trying to publish allure report on azure devops but i got that error on generate the report task :
##[warning]Failed to publish test run data: System.ArgumentException: Unknown test runner
In my baseconf.js the runner: 'local',
Where is my mistake. should i change the runner to remote and how to do it?
I can reproduce this issue And when I click on the Allure report page, I get the error 404.
This should be a issue with the extension Allure Test Reports, we recommend that you raise this issue to here, they will investigate the issue and help us solve it.
In addition, It seems that they are working on a second version, you could also check this page.
Related
SO far i can run the pipeline manually and it runs my testcafe tests with the "node myTests.js" command.
my pipeline run
My file myTests.js looks like this:
myTests.js
I followed this tutorial: https://learn.microsoft.com/en-us/azure/devops/test/run-automated-tests-from-test-hub?view=azure-devops
I tried to associated an test to my Testplan via the REST API, i guess theres some problem. because i can name it whatever i want and it just runs it without errors:my testcase association
When i run a testcase it says it found an automated test and it runs it without errors, the VsTest Job runs but with a warning:
2021-05-18T09:16:32.7619103Z Source filter: *test.dll,!*TestAdapter.dll,!\obj*
2021-05-18T09:16:32.7879061Z ##[warning]No test sources found matching the given filter '*,!\obj**'
Any ideas what im doing wrong? I just want to run my pipeline or my test when im running a testcase in my testplans.
Azure DevOps: How can i connect Testcafe-tests to a testcase?
I am afraid you could not connect the Testcafe-tests to a testcase at this moment.
According to the document Run automated tests from test plans:
You will need:
A Team Build pipeline that generates builds containing the test
binaries.
That is the reason why you get the error No test sources found matching the given filter '*test.dll,!*TestAdapter.dll,!\obj*.
We could build and test the Testcafe-tests in the azure devops pipeline.
Please check the document Integrate TestCafe with Azure DevOps for some more details.
I made some researches but still didn't figured out this problem.
So, I made an NUnit test project, selenium with c#.
Tried to add in AzureDevops pipeline.
here is the configuration in azure
I'm getting the following error -
I Tried to change those parameters. but didn't get any other result/error.
The pipeline configuration is expecting the tests in the dll with the format **\testhost.*test*.dll. But your solution does not have any projects matching that convention.
Either you need to update the pipeline configuration to match the dll's in your project or have your tests in a different project. But you will still need to update the dll pattern as I am not sure what 'testhost' is in that?
Be sure to add the NUnit Test Adapter nuget to your project containing the tests.
See also:
https://stackoverflow.com/a/43008337/736079
When you run the test task initially it will fail. But when you see the error you can get the path of the dll files in working directory/in agent. Add that path in your task and re-run
I have an Azure build pipeline that runs a Checkmarx scan on a regular basis. Once this runs, the build log is populated with the amount of 'high', 'medium', 'low' severity results are found during the scan. I'd like to access this log to be able to act upon the 'high' severity results found (specifically, I'll be creating an Azure DevOps task).
Is there a way to read the Build log during the actual build? I've found that there is a 'Get Build Log' Azure endpoint but that seems odd to call an endpoint from a build to read its own logs.
Additionally, my first idea was to simply export the Checkmarx results within the Checkmarx step but that doesn't seem to be an option.
Is there a way to read the Build log during the actual build?
You could use the REST API Builds - Get Build Logs:
GET https://dev.azure.com/{organization}/{project}/_apis/build/builds/{buildId}/logs?api-version=5.1
Then we could grab the url from the response body to download the last log and parse the log find out the 'high' severity results.
There is a similar thread about this issue, you could check it for some more info.
Hope this helps.
Triggering Test Automation after creating pipeline release in Azure cloud. After test execution gets completed, not able to see test results back in azure. Seeing error log as TestResult.xml does not matches 'NUnit' test results format.
Technical Stack : C#, NUnit, Selenium , Azure
2019-11-11T07:48:53.6045046Z ##[section]Starting: UI: Publish Test Results **\*.xml
2019-11-11T07:48:53.6045046Z ==============================================================================
2019-11-11T07:48:53.6045046Z Task : Publish Test Results
2019-11-11T07:48:53.6045046Z Description : Publish test results to Azure Pipelines
2019-11-11T07:48:53.6045046Z Version : 2.158.0
2019-11-11T07:48:53.6045046Z Author : Microsoft Corporation
2019-11-11T07:48:53.6045046Z Help : [Learn more about this task](https://go.microsoft.com/fwlink/?LinkID=613742)
2019-11-11T07:48:53.6045046Z ==============================================================================
2019-11-11T07:48:54.3203486Z [command]"C:\Program Files\dotnet\dotnet.exe" --version
2019-11-11T07:48:54.4922262Z 2.2.108
2019-11-11T07:48:54.4922262Z [command]C:\Vsts\Agent-1\_work\_tasks\PublishTestResults_0b0f01ed-7dde-43ff-9cbb-e48954daf9b1\2.158.0\modules\TestResultsPublisher.exe #C:\Vsts\Agent-1\_work\_temp\b5ad22b0-0457-11ea-9e79-9db0871d9ecd.txt
2019-11-11T07:49:36.6438230Z ##[warning]Invalid results file. Make sure the result format of the file 'C:\TestAutomation\QA\TestResult.xml' matches 'NUnit' test results format.
2019-11-11T07:49:36.6438230Z ##[section]Async Command Start: Publish test results
2019-11-11T07:49:36.6438230Z ##[section]Async Command End: Publish test results
2019-11-11T07:49:36.6438230Z ##[section]Finishing: UI: Publish Test Results **\*.xml
Donot know if you are using nunit#3. It is a known issue for nunit#3. VSTS does not support NUnit3 format currently.
You can go vote it up and keep track on it here.
Currently you can try the workaround to using Nunit-v2-reslut-writer, or add a powershell task to run the transform scripts as suggested in above open issue.
I'm running into a strange problem whenever I start a particular build, and I can't get my head around it.
I just imported an existing VSTS-repository into my new GIT-Repository on Azure DevOps. My next step is to create a Build-pipeline which should lead to an artifact which I can deploy. For the company I work for I've done this many times, but I've never seen this error before.
The buildpipeline is setup, and as soon as I start a build it immediately fails with the following error;
Hopefully somebody can help out in resolving this.
UPDATE - Added settings for retrieving sources
After posting the second screenshot and going through everything again properly, I saw that I didn't point the Build Pipeline to the proper GIT-Repository in Azure Devops. After updating this, the issue was resolved.