ms-structural / ms-structural/femdesign-api
Automatic testing of all examples
Open
Nobody has claimed this yet.
priority:now
- Dominant language
- C#
- Stars
- 51
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
It is common that we accidentally break something in the examples without noticing. This is especially true for Grasshopper where the component input might change and there are no compile errors to safeguard such as in C#.
- #592
- #593
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the examples and the completed issues #592 and #593 first, since the issue provides no file or test entry point. Define the scope of automatic coverage for the examples, including Grasshopper components, and consider the work complete when regressions in those examples are detected by the project’s test process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100