Zenoss QA Overview
Welcome to the Zenoss Test Case Repository. This page serves as both the high-level summary document for Zenoss QA as well as the repository for the Zenoss Core, Pro, and Enterprise test cases. These test cases can be edited by anyone with the proper Trac access. As a software project with a significant user community, we decided to locate our test cases someplace that the community can execute and update. Please email Brian with any questions or before you make large-scale content revisions. As with all Wikis, this Wiki is a constant work in progress, and we can't finish without your help.
Test Environment
As everyone here knows, the Zenoss product is a powerful tool for monitoring diverse network environments. It is also scalable and customizable, to model greater numbers of more diverse devices as time progresses. As such, any test environment that we maintain will inherently be missing machines that are available "in the wild". Furthermore, there are machines that are esoteric and/or prohibitively expensive, and these are not practical to maintain in a dedicated QA lab.
Zenoss is working to configure a consistent test environment that internal testers can model and use when testing the Zenoss product. This environment will consist of a reasonable and manageable number of devices, currently expected to contain 25 total devices, and would be *the* group of machines that Zenoss models when testing new builds & functionality. It also allows for known monitoring values; for example, that the following services should always be seen via WMI, that the following interfaces should be discovered and modeled, etc.
Click here for more information on the Zenoss Test Environment, for example what devices are and are not included.
Click Here for How to make Vmware boxes for testing and such
Sample Test Case (Stub)
Zenoss will use a standard stub test case for all new test case creation. Please make sure, if you add a test case that doesn't already exist, that you follow our naming convention, TestCase-{Test-Component}. All test cases must be prefaced by the "TestCase-" string. As with all things, note that this Test Case Stub is being constantly updated as we progress with testing; Zenoss QA will update older test cases with any formatting changes as needed.
Click here for the sample test case stub, and copy/paste the pre-formatted section of text into your empty Wiki page.
Zenoss 2.3 Test Execution Document
We are tracking the 2.3 Test Execution on Google Docs at http://spreadsheets.google.com/a/zenossinc.com/ccc?key=pTjLoJ3i0aWLpCpXEZs68RQ&hl=en.
Zenoss TRAC Defect Template
For enhancements being entered in track, feel free to make your recommendations in whatever format you find most effect. However, for defects, please use the following framework (enter all fields if possible):
Zenoss Test Case Repository
Test cases are organized by basic area; if you are unsure of where a given test case should be located, please contact Brian.
Build Smoke Tests
- Zenoss Product Installation
- Login/User/Email
- Discovery & Modeling
- Monitoring, & Performance
- Smoke Document by Dahl (integrate)
Automation Tests
Distributed Collector
Regression Suite
Discovery and Modeling
Distributed Collector Discovery and Modeling
| Distributed Collector Overview |
VMWare
https://dev.zenoss.com/tracint/wiki/VMware1_0TestCaseDiscussion
Monitoring and Alerting
User Interface and Displays
Installation Tests
| Source Installation Tests | BIN Installation Tests? | Appliance/VM Installation Tests? | RPM Installation Tests |
Upgrades Tests
| Source Upgrade Tests? | BIN Upgrade Tests? | Appliance/VM Upgrade Tests? |
ZenPack-Specific Tests
Functional Test Script
The current Google Docs testcase, 51 sections.
