That’s what have triggered me to do some investigation. Test explorer and the docker container does not work. However, the running experience is not the same: the integration between the This is exactly the same behavior we get in an ASP.NET or Console project. The result: a Dockerfile is added to the solution andĪ new Docker launch profile is added to the list of profiles. Though, the option is stillĪvailable via Solution Explorer. Unlike ASP.NET projects, in Unit Test projects we don’t have the option “Enableĭocker Support” while creating the project. public void Test_is_running_in_linux_container ( ) Let’s create a xUnit (my test framework of choice) testįor demonstrating purposes, let’s create a simple test that asserts that the Specific test is failing in Linux, and you want to debug it. NET Core project that would be deployed in Windows, but also in Linux, and a So, imagine that you are working with Visual Studio 2019 on Windows, building a Profile was selected, I thought that the tests would be running/debugging inside I was evenĮxpecting that I could use the VS Test Explorer: as long as the Docker launch My expectation was that the experience of running or debugging unit tests inĬontainers would be exactly the same as ASP.NET or Console apps. In this case, they specify the browser in which the tests should run and the relative path to the test file.Is great, providing a great experience for running and debugging ASP.NET andĬonsole applications in docker containers. args - command line arguments passed to the launched program.In this case, this file is the TestCafe module. program - path to the executed JS file.name - specifies the configuration name.Set to launch since this configuration launches a program.
The legacy protocol has issues with source map support, therefore newer versions of Node.js are recommended. In that case, Node.js uses a legacy debugger protocol.
Note that the inspector protocol is supported in Node.js v6.3 (or v6.9 for Windows) or later. protocol - specifies the Node.js debugger wire protocol .type - specifies the configuration type.This configuration contains the following attributes: Before you debug in Visual Studio Code, ensure that your root test directory contains a package.json file that includes testcafe in the devDependencies section.
0 kommentar(er)
