multi project support

[DerHerrGammler]

Is there a possible way to configure it to send to two different projects?

[boxblinkracer]

hi there
nope, not at the moment
but i'm open for ideas

but wouldnt that duplicate a lot more settings like milestoneIDs, suiteIds and more?
and also to provide multiple TestCase IDs (which would already work)

so a lot to setup.....what would be the use case when you need multiple projects?

thanks :)

[DerHerrGammler]

I'm totaly not sure about anything because i'm new to testrail and my company just want to use this package to get the results in testrail but I saw that we had multiple projects their.

ATM I dont know if we need a multi project configuration and/or why we need it so I asks that in case :P

thanks for your quick answer. I will have a look at our current TestRail usage and configuration and hope that we don't need it :P

[boxblinkracer]

ah ok i see.

yeah just let me know. would love to support you when you need changes that make sense :)

and if you have a question feel free to ask

[DerHerrGammler]

OK what I saw now is that we probably don't need multi project setup but multi suits.

Just as an example. We have multiple QA teams writing Tests and every team has its own suit and add new tests to their suit. So Team 1 in suitId S1 would add cases C1, C2 and C3 and team 2 will and in their suit S2 the cases C4, C5 and C6.

When i see it correctly I only could use one suit so only team 1 or team 2 could use this integration. Not both at the same time.

My idea is that we could probably configure the suitId for every case that is defined like
C123: testing something and when you define a case like S1-C2: test for team 1 it will run this against suitId S1.

When I saw it correctly we need to setup every suit before we run our tests so we could add a configuration array like suitIds: ["S1", "S2"] so that we can initilaize the runs for those suits before we run the tests.

What do you think about it?