Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need a extension setting for choosing what paths to use to list test #20

Closed
johlju opened this issue Aug 11, 2021 · 2 comments
Closed
Assignees
Labels
enhancement New feature or request
Projects

Comments

@johlju
Copy link
Contributor

johlju commented Aug 11, 2021

When doing development for the repo SqlServerDsc we run

.\build.ps1 -ResolveDependency -Tasks build

that gives us a folder structure like the following (just the important parts listed):

C:\source
└───SqlServerDsc
    │   build.ps1
    │
    ├───output
    │   └───RequiredModules
    │   └───SqlServerDsc
    ├───source
    │
    └───tests
        └───QA
                module.tests.ps1
        └───Unit
        └───Integration

In the folder RequiredModules we have a lot of dependencies for the pipeline (among other things). The problem is that those modules in that folder contain a lot of tests that are also listed, but they are not part of the project.

The test from the red mark are not part of the SqlServerDsc project.
image

Suggest adding a extension settings for setting what paths are used for reading tests, e.g. ProjectTestFolders.

@JustinGrote JustinGrote added the enhancement New feature or request label Aug 11, 2021
@JustinGrote JustinGrote added this to To Do in Roadmap via automation Aug 11, 2021
@JustinGrote
Copy link
Collaborator

Thanks, this is on the to-do list after getting everything stable.

@johlju
Copy link
Contributor Author

johlju commented Aug 24, 2021

Using the latest commit (6ffbaad) this now works perfectly

{
    "pester.testFilePath": [
        "[tT]ests/[uU]nit/*.[tT]ests.[pP][sS]1"
    ]
}

image

Roadmap automation moved this from To Do to Done Aug 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

No branches or pull requests

2 participants