testautomation | Test Automation Repository contains Selenium Webdriver | Functional Testing library

If you use this in release pipeline you can move task to build pipeline and publish file as artifact. That's one option.

Another option can be Azure File Copy task so you will copy your file to Azure Blob and later you can inspect your file.

Of course, you can also get your file from a place where you host your test env. (you didn't mention where it is so I can't say here more).

If you have FTP available you can copy your file there FTP Upload task.

If you just print your file to the output your secrets will be replaced with *** so you may not be able to verify as you want to.

You should specify the (output of the) TestProject to run, not the individual files that contain a test. The test runner cannot execute a .cs file.
So in short; the failing test doesn't run successful in an Azure DevOps pipeline... it doesn't run in the pipeline at all.

Test files
Run tests from the specified files. Ordered tests and webtests can be run by specifying the .orderedtest and .webtest files respectively. To run .webtest, Visual Studio 2017 Update 4 or higher is needed. The file paths are relative to the search folder. Supports multiple lines of minimatch patterns.

Source Visual Studio Test task - Arguments

Possibly interesting as well: more info on File matching patterns reference

EDIT:

what would be the proper Source Path to my tests?

Of course that depends on the name of your test project. Looking at your screenshots, you could use **/*.Tests.dll. This recursively matches all the assemblies where the name ends with .Tests.dll.
Since your project's name is NR.TestAutomation.Tests, the assembly should be named NR.TestAutomation.Tests.dll so it will match. It's also ready for future additions of test projects, as long as their name ends with .Tests.

The error IllegalStateException: The driver is not executable: /Users/roja/Documents/GitHub/testautomation/chromedrivers/chromedriver_osx says it all. You have to make exactly 4 changes as follows :

• Change Webdriver.chrome.driver as :

Looks like a firewall issue. The file is there and there's no reason for the Spring maven repos to deny you access to them unless maybe you've been blacklisted for some reason.

First check whether the machine you're trying to run the build on is connected to the internet, and whether there are firewalls blocking traffic to and from it.

Most likely that's your problem.

• Read the JSON file and convert it using ConvertFrom-Json.
• Select the id and name properties and convert back to json
• Write the newly created json to file

Something like this:

i've struggled with this as well. for me, the issue was that the path in "--alluredir" parameter didn't match one of the allure plugin.

make sure the path of --alluredir is:

1. must be folder called exactly 'allure-result' (at least for my version the configuration of the allure jenkins plugin is a lie)
2. relative to jenkins workspace and to your specific build folder inside the workspace

so, it should look something like:

The first thing that jumps out at me is that you're not setting -XX:MaxDirectMemorySize to anything specific. This means it defaults to the same as the max heap size. Given that you're trying to create 4(?) caches with 200MB of offheap each you may well just be running out of offheap space. Try adding a suitable value when you spawn the JVM?

Your data provider method should return pojos:

As in here, you might need to add environment variables (MAVEN_HOME) and complete the PATH (with the one for mvn)

Or at least do the same in your script.sh, meaning don't assume that you would inherit all of your user session environment in a cron session.