[Specflow+ LiviingDocs] - In order to track progress against multiple jira projects, as a project manager, I want living docs + to support multiple work items

David Galloway

December 14, 2021 13:36

We use multiple jira projects to track different aspects of our work, for example internal work and external requests. We run the same tests against internal and external requests as it is the same sysytem under test. Currently we can only gnerate living docs against 1 jira project at a time. It would be really helpful if we could specify multiple work item prefixes and templates so that we could generate 1 set of living docs as a single source of truth.

this fails :

 

PS C:\Users\davidg\source\repos\odin-e2e-test\ACME.CMS\bin\Debug\netcoreapp3.1> livingdoc.exe test-assembly .\ACME.CMS.dll -t .\TestExecution.json --work-item-prefix INT- --work-item-url-template https://acme.atlassian.net/browse/INT-{id} --work-item-prefix EXT- --work-item-url-template https://acme.atlassian.net/browse/EXT-{id}

livingdoc.exe : The command parameter was already specified.

At line:1 char:1

+ livingdoc.exe test-assembly .\ACME.CMS.dll -t .\TestExecutio ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidArgument: (:) [], ParameterBindingException

+ FullyQualifiedErrorId : ParameterSpecifiedAlready

 

3.9.5+g1ce8c747c9

 

 

it would be good if duplicate parmeters were supported or an alternative syntax for specifiyin a list of tmeplates & prefixes, something like

 

livingdoc.exe test-assembly .\ACME.CMS.dll -t .\TestExecution.json --work-item-prefix [INT-,EXT-] --work-item-url-template https://acme.atlassian.net/browse/{{ [INT-,EXT-] }}{id}

although allowing duplicates would probably be easier to understand

2

• 

  Robin Hughes

  January 19, 2022 12:00

  It would be great if we could tag our scenarios with multiple Azure Dev Ops work items and have this reflected on the living doc.

  0

Please sign in to leave a comment.