You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TSC agreed to discuss & investigate whether or not each of the Zowe squads has a satisfactory inventory of SYSTEM TEST. The outcome of the discussion should include the following:
An EPIC that all squads can leverage to track work related to this item
A roadmap item that describes the goal and strategy for achieving MVP System Tests
A document that describes current process and dependencies (i.e. are we depending on Vendor hardware vs. Community Hardware)?
A method of tracking tech-debt items that need to be addressed by squad (i.e. upgrade to current release of Java, Node etc.)
The text was updated successfully, but these errors were encountered:
As Zowe, we have limited means to verify all the potential configurations and combinations of the hardware and software all the user have installed.
System tests suite should be:
a way to validate that Zowe works properly for us as a Zowe in our nightly pipelines
for vendors to validate the same on further combinations of hardware and software
for users to validate that Zowe is properly installed and configured
With such a suite we can properly validate support for new technologies that we want to support e.g. new z/OS, Java, Node.js versions and others. On top of that the support providers can help assure the customers that the Zowe will run on any combination of hardware and software they may need.
To achieve this we need to:
define key functionality for Zowe including client and server side
Each squad define a suite testing key functionalities
TSC agreed to discuss & investigate whether or not each of the Zowe squads has a satisfactory inventory of SYSTEM TEST. The outcome of the discussion should include the following:
The text was updated successfully, but these errors were encountered: