Add requirements specification and automated trace matrix generation#44
Add requirements specification and automated trace matrix generation#44Malcolmnixon merged 7 commits intomainfrom
Conversation
Co-authored-by: Malcolmnixon <1863707+Malcolmnixon@users.noreply.github.com>
Co-authored-by: Malcolmnixon <1863707+Malcolmnixon@users.noreply.github.com>
Co-authored-by: Malcolmnixon <1863707+Malcolmnixon@users.noreply.github.com>
… space Co-authored-by: Malcolmnixon <1863707+Malcolmnixon@users.noreply.github.com>
Malcolmnixon
left a comment
There was a problem hiding this comment.
Consider if the requirements.yaml file can be shrunk a bit - only basic test linkage to prove functionality.
… mappings Co-authored-by: Malcolmnixon <1863707+Malcolmnixon@users.noreply.github.com>
Simplified requirements.yaml in commit f27f6a7. Reduced from 30 to 29 requirements by removing CLI-004 (silent mode), and removed unnecessary test mappings from CLI-002 and CLI-003. Now has 23 of 29 requirements with test coverage. |
.github/workflows/build.yaml
Outdated
| --configuration Release | ||
| --verbosity normal | ||
| --collect "XPlat Code Coverage;Format=opencover" | ||
| --logger "trx;LogFileName=test-results.trx" |
There was a problem hiding this comment.
Please add the OS to the test-results file name - may be used later to support proving support for different operating systems.
There was a problem hiding this comment.
Added OS to test-results filename in commit cd11d2b. Now generates files like test-results-windows-latest.trx and test-results-ubuntu-latest.trx.
.github/workflows/build_docs.yaml
Outdated
| - name: Restore dotnet tools | ||
| run: dotnet tool restore | ||
|
|
||
| - name: Generate Requirements Report |
There was a problem hiding this comment.
The Generate Requirements Report and Generate Trace Matrix steps should be merged - both reports can be generated simultaneously.
There was a problem hiding this comment.
Merged both steps into "Generate Requirements Report and Trace Matrix" in commit cd11d2b. Now both reports are generated in a single reqstream invocation.
.github/workflows/build_on_push.yaml
Outdated
| name: Build Documentation | ||
| needs: quality-checks | ||
| needs: | ||
| - build-windows |
There was a problem hiding this comment.
Please add comments to the needs lines indicating they are needed for test results.
There was a problem hiding this comment.
Added inline comments in commit cd11d2b indicating both dependencies are needed for test results.
.gitignore
Outdated
| docs/guide/*.html | ||
| docs/guide/*.pdf | ||
| docs/requirements/*.html | ||
| docs/requirements/*.pdf |
There was a problem hiding this comment.
The PDFs aren't created in the guide, requirements, or tracematrix folders, and can be removed from .gitignore
There was a problem hiding this comment.
Removed PDF patterns from subdirectories in commit cd11d2b. Only docs/*.pdf is needed since all PDFs are created directly in the docs folder.
…ps, add comments, clean gitignore Co-authored-by: Malcolmnixon <1863707+Malcolmnixon@users.noreply.github.com>
Plan for Adding ReqStream Requirements
requirements.yamlfile with basic requirements for ReqStream tool.config/dotnet-tools.jsondocs/requirements/folder structuretitle.txtfor requirements documentdefinition.yamlfor pandoc configurationintroduction.mdfor requirements introductiondocs/tracematrix/folder structuretitle.txtfor trace matrix documentdefinition.yamlfor pandoc configurationintroduction.mdfor trace matrix introductionbuild_docs.yamlworkflow.gitignoreto exclude generated markdown and PDFsbuild.yamlto save and upload TRX test resultsbuild_docs.yamlto download and use test resultsbuild_on_push.yamlto ensure docs build after tests completeSummary
Successfully implemented ReqStream requirements documentation infrastructure:
✅ Created 29 requirements covering essential ReqStream functionality
✅ Linked 23 requirements to existing test methods for traceability
✅ Set up automated documentation generation in CI/CD pipeline
✅ Test results are captured as TRX files with OS identifier and used for trace matrix generation
✅ All quality checks passed (markdown lint, spell check, YAML lint, code review, security scan)
✅ Simplified requirements based on review feedback
✅ Optimized workflow efficiency and clarity
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.