METplus Coordinated 6.1.0-beta1 Testing #2871
bikegeek
started this conversation in
Release Acceptance Testing
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Listed below are summaries of the new features, enhancements, and bugfixes included in all development cycles (beta1, beta2, and release candidate 1) for each software component of the METplus Coordinated 5.1.0 release. These tables summarize the status of external acceptance testing.
Note that status of earlier testing for METplus Coordinated 5.1.0-beta1 Testing and METplus Coordinated 5.1.0-beta2 Testing has been copied into this discussion.
Please see the METplus 5.1 Existing Builds page to see where the release candidate versions are already installed.
Instructions
For each line in these tables, the
Tester
listed should test the release candidate to confirm the changes work as expected in their environment.Copy/paste the following template into your issue or discussion comment:
The
Tester
is set toNA
for any issues that do not require external acceptance testing.Integration Testing
Integration Testing refers to testing functionality not specifically tied to a single GitHub issue. The largest category here is testing existing use cases in your environment (e.g. NOAA/EMC testing their EMC Vx System use cases). This also includes testing new features across multiple METplus components.
Users are encouraged to test their existing use cases with the METplus release candidate and report their results as comments on this discussion (see Instructions above). Please indicate the name of the use case if not already listed in the table below. Comments about expected results (PASS) and unexpected results (FAIL) are welcome. The METplus team will add a row for the use case and summarize those comments in the table below.
(OPEN,
PASS,
FAIL)
Repository Testing: METplus Wrappers (Project Board)
Testing of specific METplus Wrapper issues (new features, enhancements, and bugfixes).
(OPEN,
PASS,
FAIL)
The majority of the changes to METplus wrappers were tested when the changes were made, so testing of these specific issues may not be necessary. However, it would be good to perform general testing of existing METplus use cases to ensure that any changes have not caused unexpected bugs. This should be covered in the "Integrated Testing" section.
Repository Testing: MET (Project Board)
Testing of specific MET issues (new features, enhancements, and bugfixes).
(OPEN,
PASS,
FAIL)
Repository Testing: METplus Analysis (Project Board)
Testing of specific METplus Analysis (METdataio, METcalcpy, METplotpy, METviewer, and METexpress) issues (new features, enhancements, and bugfixes).
(OPEN,
PASS,
FAIL)
(OPEN,
PASS,
FAIL)
(OPEN,
PASS,
FAIL)
(OPEN,
PASS,
FAIL)
(OPEN,
PASS,
FAIL)
Beta Was this translation helpful? Give feedback.
All reactions