| Reviewer | ID | Location in the test spec (use links if possible) | Comments/Discussion | Resolved -- YES/NO |
|---|
| Satish Viswanatham | SV01 NEW/ACTI-05 | 1. Test Cases for Activation | Need to also test CLI start-domain command | |
| Satish Viswanatham | SV02 NEW/GENR-05 | 2. Test Cases for general features | Test once a module is visited it should be displayed differently than un-visited modules | |
| Satish Viswanatham | SV03 NEW/AVUP-07 | 3. Test Cases for Available Updates | Should test Update of Update Center | |
| Satish Viswanatham | SV04 NEW/AVSW-07 | 5. Test Cases for Available Software | If a module is un-installed, it should be still shown as available module. | |
| Nazrul Islam | NI01 NEW | 2. Test Cases for general features | Please test resize of the window. | |
| Nazrul Islam | NI02 NEW | 2. Test Cases for general features | Please test logging features such as log rotation, etc. | |
| Nazrul Islam | NI03 NEW | 2. Test Cases for general features | Please test update of Update Center. This feature should behave similar to firefox update. | |
| Nazrul Islam | NI04 NEW | 2. Test Cases for general features | Please test jar signing feature so that downloaded bits are not compromised during transport. | |
| Nazrul Islam | NI05 NEW | 2. Test Cases for general features | Please test update of an installed software such as Portlet container. | |
| Nazrul Islam | NI06 NEW | 2. Test Cases for general features | Please test context sensitive help. We need to make sure the instructions are clear. | |
| Nazrul Islam | NI07 NEW | 2. Test Cases for general features | Please make sure each module has clear description. | |
| Nazrul Islam | NI08 NEW | 2. Test Cases for general features | Please test module dependency resolution. | |
| Nazrul Islam | NI09 NEW | 2. Test Cases for general features | Please test the server side hosted as http/https. For example, user should be able to host the catalog on https and nbm/jar may reside on http. | |
| Snjezana Sevo-Zenzerovic | SSZ01 NEW | Test Plan 6.1Test Approach | "Addon component update" as feature is misleading since it might imply only subset of components. Update of all supported component types should be tested. | |
| Snjezana Sevo-Zenzerovic | SSZ02 NEW | Specification ACTI-04 | Invocation of update center client from admin GUI not available at this time. However, there should be a test case to check if admin GUI correctly notifies user about available updates. Also, see SV01 - we should have test case to test update notification and startup from asadmin. | |
| Snjezana Sevo-Zenzerovic | SSZ03 NEW | Specification 4. Test Cases for Installed Software | In case of update center client delivered with SDK distributions, installed software list must come prepopulated with list of components which are installed as part of appropriate SDK installations. It should also be possible to uninstall such components. Please add test case for this. | |
| Snjezana Sevo-Zenzerovic | SSZ04 NEW | Specification 7. Test Cases for Preferences | Test cases for update handling preferences (notify only, download, download and install) are missing. Please add those. | |
| Snjezana Sevo-Zenzerovic | SSZ05 NEW | Specification General | For all test cases dealing with component installation, update or uninstallation, we should test those operations on all supported module types (i.e. archives, applications, addon installers and addon configurators). | |
| Snjezana Sevo-Zenzerovic | SSZ06 NEW | Specification 4. Test Cases for Available Software | Add test case for archive modules which contain config.properties file, in which case UI should prompt for configuration parameters at installation time. | |
| Rajeshwar Patil | RP01 NEW | Test Cases for dependency resolution | Add test cases for dependency management. Please refer to Update Center Module Dependencies for test cases to add. | |
| Rajeshwar Patil | RP02 NEW | Test Cases for jar signature verification | Add test cases for jar signature/verification support in Update Center. | |