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

Ability to use mulitple .taskcat.yml from scopes #673

Open
TejjeT opened this issue Jul 30, 2021 · 5 comments
Open

Ability to use mulitple .taskcat.yml from scopes #673

TejjeT opened this issue Jul 30, 2021 · 5 comments

Comments

@TejjeT
Copy link

TejjeT commented Jul 30, 2021

Hello ,

At present taskcat uses .taskcat.yml from a dedicated project. It will be helpful to have the ability to auto-include additional
.taskcat.yml in subfolders in scope. if this is already possible, could you provide a way for me to do this. This will help me have different sets of tests while dev and ci ( more like integration tests , if I have 100 different tests) , I know we can run a specific tests using -t but having a config helps

@andrew-glenn
Copy link
Contributor

andrew-glenn commented Jul 30, 2021

Interesting use case. Would using -p subfolder accomplish what you're looking for?

For what it's worth, while I understand the ask, I don't understand how it would be used in practice.

Can you elaborate a bit on the pain here ?

Edit: Thoughts after I hit submit: This behavior sounds very similar to how unit tests are structured. Is the intent to run taskcat test run at the root and have the subconfigs run, but not necessarily need to clutter your project config with your 100 specific test cases?

@TejjeT
Copy link
Author

TejjeT commented Aug 25, 2021

Yes that is exactly what I was referring to , I could separate the tests into the corresponding sub folders , and I could choose to Run them based on the the current working directory from which I am Running.

This could also mean I could have more than one taskcat files ( obvisously with different names) in a given subdirectory

@andrew-glenn
Copy link
Contributor

@TejjeT

The only remaining question I have is around project root.

❯ tree . -a
.
├── .taskcat.yml
├── testA
│   └── .taskcat.yml
├── testB
│   └── .taskcat.yml
├── testC
│   └── .taskcat.yml
└── testD
    └── .taskcat.yml

In my mind, each of these tests could be an independent project. Executing taskcat test run from the root would collolate each of those tests and run them at once via one execution, rather than independently running taskcat against testA, then testB etc.

Does this track with your intended behavior?

@TejjeT
Copy link
Author

TejjeT commented Jan 4, 2022

Sorry for super late response, but yes what you described is exactly what I was asking for.

@sahu-sunil
Copy link

Any updates on this?
I also have similar kind of requirement wherein multiple templates are in different directories, and would like to run them all together by having their own .taskcat.yml file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants