[New Process Improvement Need]: Governing how to keep automated tests up-to-date
Open
Nobody has claimed this yet.
governance
low complexity
more requested
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Checked for duplicates
Yes - I've already checked
Category
Governance - people, personnel, organization, etc.
Describe the need
We have a need for better governance approaches for keeping automated tests up-to-date per software changes - esp. with multiple developers.
Contributor guide
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
No files, tests, or entry points are identified in the issue. Start by clarifying the intended governance scope for keeping automated tests aligned with software changes across multiple developers, then define what documented process and evidence would count as done.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100