Skip to content

Confusing test screen when working with a monorepo #22896

Open
@NicolasTr

Description

@NicolasTr

The test screen is confusing when working with a monorepo.

For example, let's use the following layout:

.
└── domains
    ├── domain-A
    │   └── services
    │       └── api
    │           └── test_something.py
    ├── domain-B
    │   └── services
    │       └── api
    │           └── test_something.py
    └── domain-C
        └── services
            └── api
                └── test_something.py

Each API would be completely independent (dependencies, ...).

In VS Code, they can easily be added to the same workspace:

{
	"folders": [
		{
			"name": "A - api",
			"path": "../domains/domain-A/services/api"
		},
		{
			"name": "B - api",
			"path": "../domains/domain-B/services/api"
		},
		{
			"name": "C - api",
			"path": "../domains/domain-C/services/api"
		}
	],
	"settings": {}
}

However, all services will show as api on the test screen:

Screenshot 2024-02-10 at 20 19 05

I would have expected:

  1. The top-level objects in the tree to use the VS Code folder name rather than the filesystem name (blue arrows)
  2. Same for the error messages (red arrow)

I managed to track (2) to this line, so I assume (1) is also using fsPath.

The VS Code documentation, says the following about fsPath:

The resulting string shall not be used for display purposes but for disk operations, like readFile et al.

What do you think?

Metadata

Metadata

Assignees

Labels

area-testingcommunity askFeature request that the community expressed interest infeature-requestRequest for new features or functionalityneeds proposalNeed to make some design decisions

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions