Add testing.yaml
testing workflow
#539
Labels
alert: NEED CYCLE ASSIGNMENT
Need to assign to a release development cycle
alert: NEED MORE DEFINITION
Not yet actionable, additional definition required
component: testing
Software testing issue
priority: high
High Priority
requestor: METplus Team
METplus Development Team
type: new feature
Make it do something new
Milestone
Describe the New Feature
Other METplus components include an automated
testing.yaml
testing workflow that's run through GitHub actions for each Pull Request. Recommend adding this automated testing for METviewer as well with logic very similar to the logic in METplus and MET.This is related to work will help with issue: https://github.com/dtcenter/METplus-Internal/issues/36
Many more details need to be added here.
Acceptance Testing
List input data types and sources.
Describe tests required for new functionality.
Time Estimate
Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.
Sub-Issues
Consider breaking the new feature down into sub-issues.
- [ ] If JUnit tests do not exist, create them
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
Define the source of funding and account keys here or state NONE.
Define the Metadata
Assignee
Labels
Milestone and Projects
Define Related Issue(s)
Consider the impact to the other METplus components.
New Feature Checklist
See the METplus Workflow for details.
Branch name:
feature_<Issue Number>_<Description>
Pull request:
feature <Issue Number> <Description>
Select: Reviewer(s) and Development issue
Select: Milestone as the next official version
Select: METviewer-X.Y.Z Development project for development toward the next official release
The text was updated successfully, but these errors were encountered: